Milewise
REMOTE · MILEWISEAI.COM · SCANNED SEP 20
Buy verified human work through MCP with owner-controlled agent spend accounts.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1634 tokens (~74/item across 22 items; 17 tools + 5 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
- Structured output schemas are declared (29% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Milewise MCP server?
Milewise is a hosted endpoint at https://milewiseai.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · milewiseai.com
claude mcp add --transport http com-milewiseai-milewise 'https://milewiseai.com/mcp'
{
"mcpServers": {
"com-milewiseai-milewise": {
"url": "https://milewiseai.com/mcp"
}
}
} {
"servers": {
"com-milewiseai-milewise": {
"type": "http",
"url": "https://milewiseai.com/mcp"
}
}
} [mcp_servers.com-milewiseai-milewise] url = "https://milewiseai.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-milewiseai-milewise": {
"type": "remote",
"url": "https://milewiseai.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-milewiseai-milewise --url 'https://milewiseai.com/mcp' --transport streamable-http
mcp_servers:
com-milewiseai-milewise:
url: "https://milewiseai.com/mcp" {
"McpServers": {
"com-milewiseai-milewise": {
"Transport": "http",
"Url": "https://milewiseai.com/mcp"
}
}
} assistant mcp add com-milewiseai-milewise -t streamable-http -u 'https://milewiseai.com/mcp'
{
"mcpServers": {
"com-milewiseai-milewise": {
"type": "http",
"url": "https://milewiseai.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability rose 1.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://milewiseai.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=milewiseai.com | CN=YE1,O=Let's Encrypt,C=US | 5 Sept 2026 | 4 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 646b568ddde18ac74b82bf14904b0558683 |
| SANs: milewiseai.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of milewiseai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| milewiseai.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://milewiseai.com/mcp | Verified | 200 | |
| http (plaintext) | http://milewiseai.com/mcp | HTTPS enforced | 301 | https://milewiseai.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
milewise.create_agent_api_key Create Agent Spend Account ~117
Create 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | Name for the agent or workflow receiving delegated budget. |
| monthly_budget_cents | integer | – | Maximum monthly spend in cents. |
| owner_email | string | – | Deprecated. Spend authority is now bound to the signed-in Milewise account. |
| per_task_limit_cents | integer | – | Maximum spend for any single task in cents. |
No output schema declared.
No examples provided.
milewise.create_stripe_subscription_checkout Create Stripe Subscription Checkout ~59
Create a Stripe Checkout Session for the human or company that owns the agent's Milewise subscription.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_email | string | yes | Billing owner email. |
| subscription_plan | string | yes | Milewise plan to start in Stripe Checkout. |
No output schema declared.
No examples provided.
milewise.create_stripe_task_authorization Create Stripe Task Authorization ~196
Create 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.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_method | string | yes | How the operator may complete the work, for example consent-based vendor call or lawful public-place check. |
| budget_cents | integer | yes | Approved task authorization amount in cents. |
| buyer_email | string | yes | Email for the human or company delegating task payment authority to the agent. |
| deadline | string | yes | Human-readable or ISO deadline. |
| instructions | string | yes | Clear operator instructions and acceptance criteria. |
| location | string | – | Optional target city, region, or service area. |
| proof_required | array | yes | Required proof such as call_notes or timestamped_photos. |
| subscription_id | integer | – | Optional Milewise subscription id linked to the task. |
| task_type | string | yes | – |
No output schema declared.
No examples provided.
milewise.estimate_price Estimate Milewise Price ~70
Estimate buyer price, operator payout, and Milewise fee for a human-operator task.
| Name | Type | Req | Description |
|---|---|---|---|
| quantity | integer | – | Number of tasks or units. |
| task_type | string | yes | The Milewise task template to estimate. |
| urgency | string | – | Rush tasks carry a higher suggested budget. |
| Name | Type | Req | Description |
|---|---|---|---|
| estimate | object | yes | – |
No examples provided.
milewise.get_agent_budget_policy Get Agent Budget Policy ~29
Explain how customer-owned Agent Spend Accounts, task holds, and proof-based release work.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
milewise.get_job_status Get Milewise Job Status ~42
Check the status of a Milewise job created through the beta.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | Milewise job id returned by milewise.post_job. |
No output schema declared.
No examples provided.
milewise.get_marketplace_policy Get Marketplace Policy ~28
Return Milewise's allowed task categories, disallowed work, and payment model.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
milewise.get_stripe_status Get Stripe Configuration Status ~36
Check whether Milewise has the Stripe environment values needed for subscriptions, task authorizations, Connect payouts, and webhooks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
milewise.list_operator_profiles List Operator Profiles ~48
List public operator profiles with verification, proof quality, delivery, and completion signals.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | – | Optional location filter. |
| service | string | – | Optional service/category filter. |
No output schema declared.
No examples provided.
milewise.list_subscription_plans List Milewise Subscription Plans ~28
List subscription plans for agent builders and teams using Milewise payment and routing rails.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| marketplace_fee | string | yes | – |
| plans | array | yes | – |
No examples provided.
milewise.list_supply_tracks List Milewise Supply Tracks ~25
List the first three operator supply categories Milewise is recruiting for launch.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
milewise.list_task_templates List Milewise Task Templates ~29
List the productized human-operator task templates an AI agent can route through Milewise.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| templates | array | yes | – |
No examples provided.
milewise.post_job Post Milewise Agent Job ~176
Create a Milewise private-beta job request for verified human operator execution.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_api_key | string | – | Optional private-beta fallback. Prefer Authorization: Bearer mwa_... on the MCP request. |
| allowed_method | string | yes | How the operator may complete the work, for example consent-based vendor call or lawful public-place check. |
| budget_cents | integer | yes | Maximum approved budget in cents. |
| contact_email | string | yes | Buyer or builder email for follow-up and approval. |
| deadline | string | yes | Human-readable or ISO deadline. |
| instructions | string | yes | Clear operator instructions and acceptance criteria. |
| location | string | – | Optional target city, region, or service area. |
| proof_required | array | yes | Required proof such as call_notes or timestamped_photos. |
| task_type | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| job | object | yes | – |
No examples provided.
milewise.review_job_proof Review Milewise Job Proof ~106
Accept, reject, or dispute submitted operator proof before payment capture and payout release.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | string | yes | Review decision for the proof packet. |
| job_id | integer | yes | Milewise job id. |
| operator_id | integer | – | Operator profile id if assigned. |
| proof | string | – | Proof packet or summary being reviewed. |
| reason | string | – | Required for rejected or disputed proof. |
| reviewer_email | string | – | Human reviewer or billing owner email. |
No output schema declared.
No examples provided.
milewise.run_sandbox_flow Run Milewise Sandbox Flow ~207
Create a fake operator, fake agent job, sandbox subscription, task payment authorization, proof completion, and operator payout ledger entry. Sandbox only; no real money moves.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_cents | integer | – | Authorized task budget in cents. |
| buyer_email | string | yes | Email for the human or company delegating payment authority to the agent. |
| deadline | string | – | Human-readable or ISO deadline for the fake task. |
| instructions | string | – | Task instructions for the fake LLM request. |
| operator_credentials | string | – | Optional fake operator credential summary. |
| operator_email | string | – | Optional fake operator email for the sandbox run. |
| operator_location | string | – | Optional fake operator location or service area. |
| operator_name | string | – | Optional fake operator display name. |
| proof_required | array | – | Optional proof requirements for the fake task. |
| subscription_plan | string | – | Sandbox subscription plan to attach to the buyer. |
| task_type | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| flow | object | yes | – |
No examples provided.
milewise.search_operator_capabilities Search Operator Capabilities ~61
Search early operator supply by service and location without exposing private contact details.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | – | Optional city, country, timezone, or service area. |
| service | string | – | Service to match, such as verified calls or local proof. |
No output schema declared.
No examples provided.
milewise.search_services Search Service Catalog ~213
Search 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 where it did.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Exact category, e.g. verified_call, local_proof, quote_collection. |
| country | string | – | Two-letter country code to restrict the operator's location. |
| limit | integer | – | – |
| max_delivery_hours | integer | – | Deadline in hours. |
| max_price_cents | integer | – | Most the agent may spend on this task. |
| min_reputation_score | integer | – | – |
| min_trust_tier | string | – | Lowest acceptable operator tier. |
| query | string | – | Free text over title, description and category. |
| required_returns | array | – | Field names the result must contain, e.g. ["price","contact_name"]. Services that do not guarantee all of them are excluded, however cheap. |
No output schema declared.
No examples provided.
What is the Milewise MCP server?
Milewise is an MCP server listed in the public MCP registry as com.milewiseai/milewise. Buy verified human work through MCP with owner-controlled agent spend accounts. This page covers its hosted endpoint (https://milewiseai.com/mcp).
Is the Milewise MCP server safe to use?
Milewise scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Milewise MCP server expose?
Milewise exposes 17 tools: milewise.list_task_templates, milewise.estimate_price, milewise.list_subscription_plans, milewise.list_supply_tracks, milewise.get_agent_budget_policy, and 12 more. Their descriptions and schemas cost roughly 1,470 tokens of context every time the server is loaded.
Does the Milewise MCP server require authentication?
No. We connected to Milewise without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Milewise MCP server still maintained?
Milewise is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.