Milewise
REMOTE · MILEWISEAI.COM
Buy verified human work through MCP with owner-controlled agent spend accounts.
Available components
Last scanned (23 hours ago)
Scores higher than 55% of remote servers
Unreachable for 3 days in a row. Last reached 1 Nov 2026.
Category Finance and Payments
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 6 Oct 26 +1
- Stability: 0.97 → pass security
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 5 Sept 26 0
First indexed and scored.
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 4 Nov 2026 · Probed https://milewiseai.com/mcp
TLS unreached
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 Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
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 | Unreachable | ||
| http (plaintext) | http://milewiseai.com/mcp | HTTPS enforced |
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.
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'
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 70 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?
Its publisher declares that Milewise requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
Is the Milewise MCP server still maintained?
Milewise is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 1 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.