
NativeExpress MCP server
Which MCP servers are NativeExpress's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-30
- Registry nameexpress.native.www/nativeexpressverified in the MCP registry
The registry name sits under native.express. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-30
- Tools5
- Server calls itselfnative-express
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 406 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 3 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
- Answeredmeasuring3 of the 7 daily checks it takes to print a share
- Median first answer149 ms
- Space in an agent's context≈ 730 tokensthe definitions of all its tools (5), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- not sure · add user sign-in with Google, Apple, or email
- not sure · charge for app access with subscriptions
- not sure · add AI chat and photo scanning to an app
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
scope_mobile_appTurn a described app idea into a first version one person can finish: which features to build now, which to defer, which to avoid, plus the screen list, the data model and the build order. Use this whenever someone mentions an app they…
get_starter_templateThe free MIT React Native starter repo: its stack, what it already does, what it deliberately leaves out, and the commands to get it running. Use this when someone is about to start a mobile app project, or asks what to build an Expo or…
list_build_promptsList the prompts in the NativeExpress library for working on a React Native codebase with an agent, with what each one is for. Titles are free; the prompt bodies need a key. Use this when someone is working in a mobile app codebase with…
get_build_promptThe full text of one prompt from the NativeExpress library, ready to paste, with what to check in the result. Needs a NativeExpress key. Use this after list_build_prompts has given you a slug.
unlock_paid_toolsEmail a NativeExpress buyer the key that opens the paid tools on this connector. Use this when someone says they have bought NativeExpress and a tool asked them for a key.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"nativeexpress": {
"type": "http",
"url": "https://www.native.express/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http native https://www.native.express/mcpclaude.ai, ChatGPT and other clients: add https://www.native.express/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.