
Milewise AI MCP server
Which MCP servers are Milewise AI'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-24
- Registry namecom.milewiseai/milewiseverified in the MCP registry
The registry name sits under milewiseai.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-24
- Tools17
- Server calls itselfmilewise-ai
- Server version0.1.0
- Protocol version2025-11-25
On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 104 ms.
- Its tools do none of the product's use cases we checked: collect quotes from suppliers by phone; verify business details and local public places.
- Checked on 3 of the 7 days it takes to judge reliability.
Once connected
- milewise.create_agent_api_key, milewise.create_stripe_subscription_checkout, milewise.post_job, milewise.create_stripe_task_authorization change data without a sign-in: anyone with the address can call them.
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
- What an agent can do with it0 of 2 use cases
- Answeredmeasuring3 of the 7 daily checks it takes to print a share
- Median first answer149 ms
- Space in an agent's context≈ 2,760 tokensthe definitions of all its tools (17), which an agent carries on every turn
- Tool definitionsA · 96 of 100
- Typed results5 of 17 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 4 of 17
What an agent can do with it
- cannot · collect quotes from suppliers by phone
- cannot · verify business details and local public places
- not sure · research and report on specific questions
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
- Tools that change data, on a server that answers without a sign-in: milewise.create_agent_api_key, milewise.create_stripe_subscription_checkout, milewise.post_job, milewise.create_stripe_task_authorization
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 →
milewise.list_task_templatesList the productized human-operator task templates an AI agent can route through Milewise.
milewise.estimate_priceEstimate buyer price, operator payout, and Milewise fee for a human-operator task.
milewise.list_subscription_plansList subscription plans for agent builders and teams using Milewise payment and routing rails.
milewise.list_supply_tracksList the first three operator supply categories Milewise is recruiting for launch.
milewise.get_agent_budget_policyExplain how customer-owned Agent Spend Accounts, task holds, and proof-based release work.
milewise.create_agent_api_keyCreate a customer-owned Milewise Agent Spend Account with monthly and per-task controls. Requires a signed-in Milewise buyer session; the API key is returned once.
milewise.get_stripe_statusCheck whether Milewise has the Stripe environment values needed for subscriptions, task authorizations, Connect payouts, and webhooks.
milewise.create_stripe_subscription_checkoutCreate a Stripe Checkout Session for the human or company that owns the agent's Milewise subscription.
milewise.post_jobCreate a Milewise private-beta job request for verified human operator execution.
milewise.create_stripe_task_authorizationCreate a Milewise job plus a manual-capture Stripe PaymentIntent. The buyer or delegated payment flow must confirm it before dispatch; capture happens only after proof acceptance.
milewise.run_sandbox_flowCreate a fake operator, fake agent job, sandbox subscription, task payment authorization, proof completion, and operator payout ledger entry. Sandbox only; no real money moves.
milewise.get_job_statusCheck the status of a Milewise job created through the beta.
milewise.review_job_proofAccept, reject, or dispute submitted operator proof before payment capture and payout release.
milewise.list_operator_profilesList public operator profiles with verification, proof quality, delivery, and completion signals.
milewise.search_operator_capabilitiesSearch early operator supply by service and location without exposing private contact details.
milewise.search_servicesSearch productized human services an agent can buy outright. Filter by category, price, delivery time, operator trust tier, reputation, and — most usefully — the fields the service guarantees to return. Every result explains why it ranked…
milewise.get_marketplace_policyReturn Milewise's allowed task categories, disallowed work, and payment model.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"milewise": {
"type": "http",
"url": "https://milewiseai.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http milewiseai https://milewiseai.com/mcpclaude.ai, ChatGPT and other clients: add https://milewiseai.com/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.