# Milewise (remote · milewiseai.com)

Buy verified human work through MCP with owner-controlled agent spend accounts.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `milewiseai.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-milewiseai-milewise/milewiseai.md), [page](https://verifymcp.io/servers/com-milewiseai-milewise/milewiseai)

## Channel facts

- Endpoint: `https://milewiseai.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1634 tokens (~74/item across 22 items; 17 tools + 5 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 91% of tool parameters carry a description.
  - Structured output schemas are declared (29% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-milewiseai-milewise 'https://milewiseai.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-milewiseai-milewise": {
      "url": "https://milewiseai.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-milewiseai-milewise": {
      "type": "http",
      "url": "https://milewiseai.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-milewiseai-milewise]
url = "https://milewiseai.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-milewiseai-milewise": {
      "type": "remote",
      "url": "https://milewiseai.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-milewiseai-milewise --url 'https://milewiseai.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-milewiseai-milewise:
    url: "https://milewiseai.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-milewiseai-milewise": {
      "Transport": "http",
      "Url": "https://milewiseai.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-milewiseai-milewise -t streamable-http -u 'https://milewiseai.com/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 73, +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.

### 2026-09-17 (score 72, +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.

### 2026-09-15 (score 71, +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.

### 2026-09-13 (score 70, +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.

### 2026-09-11 (score 69, +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.

### 2026-09-09 (score 68, +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.

### 2026-09-07 (score 67, +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.

### 2026-09-06 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (17)

### `milewise.list_task_templates` (~29 tokens)

List Milewise Task Templates

List the productized human-operator task templates an AI agent can route through Milewise.

Output parameters:

- `templates` (array)

### `milewise.estimate_price` (~70 tokens)

Estimate Milewise Price

Estimate buyer price, operator payout, and Milewise fee for a human-operator task.

Input parameters:

- `quantity` (integer): Number of tasks or units.
- `task_type` (string, required): The Milewise task template to estimate.
- `urgency` (string): Rush tasks carry a higher suggested budget.

Output parameters:

- `estimate` (object)

### `milewise.list_subscription_plans` (~28 tokens)

List Milewise Subscription Plans

List subscription plans for agent builders and teams using Milewise payment and routing rails.

Output parameters:

- `marketplace_fee` (string)
- `plans` (array)

### `milewise.list_supply_tracks` (~25 tokens)

List Milewise Supply Tracks

List the first three operator supply categories Milewise is recruiting for launch.

### `milewise.get_agent_budget_policy` (~29 tokens)

Get Agent Budget Policy

Explain how customer-owned Agent Spend Accounts, task holds, and proof-based release work.

### `milewise.create_agent_api_key` (~117 tokens)

Create Agent Spend Account

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.

Input parameters:

- `agent_name` (string, required): 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.

### `milewise.get_stripe_status` (~36 tokens)

Get Stripe Configuration Status

Check whether Milewise has the Stripe environment values needed for subscriptions, task authorizations, Connect payouts, and webhooks.

### `milewise.create_stripe_subscription_checkout` (~59 tokens)

Create Stripe Subscription Checkout

Create a Stripe Checkout Session for the human or company that owns the agent's Milewise subscription.

Input parameters:

- `buyer_email` (string, required): Billing owner email.
- `subscription_plan` (string, required): Milewise plan to start in Stripe Checkout.

### `milewise.post_job` (~176 tokens)

Post Milewise Agent Job

Create a Milewise private-beta job request for verified human operator execution.

Input parameters:

- `agent_api_key` (string): Optional private-beta fallback. Prefer Authorization: Bearer mwa_... on the MCP request.
- `allowed_method` (string, required): How the operator may complete the work, for example consent-based vendor call or lawful public-place check.
- `budget_cents` (integer, required): Maximum approved budget in cents.
- `contact_email` (string, required): Buyer or builder email for follow-up and approval.
- `deadline` (string, required): Human-readable or ISO deadline.
- `instructions` (string, required): Clear operator instructions and acceptance criteria.
- `location` (string): Optional target city, region, or service area.
- `proof_required` (array, required): Required proof such as call_notes or timestamped_photos.
- `task_type` (string, required)

Output parameters:

- `job` (object)

### `milewise.create_stripe_task_authorization` (~196 tokens)

Create Stripe Task Authorization

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.

Input parameters:

- `allowed_method` (string, required): How the operator may complete the work, for example consent-based vendor call or lawful public-place check.
- `budget_cents` (integer, required): Approved task authorization amount in cents.
- `buyer_email` (string, required): Email for the human or company delegating task payment authority to the agent.
- `deadline` (string, required): Human-readable or ISO deadline.
- `instructions` (string, required): Clear operator instructions and acceptance criteria.
- `location` (string): Optional target city, region, or service area.
- `proof_required` (array, required): Required proof such as call_notes or timestamped_photos.
- `subscription_id` (integer): Optional Milewise subscription id linked to the task.
- `task_type` (string, required)

### `milewise.run_sandbox_flow` (~207 tokens)

Run Milewise Sandbox Flow

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.

Input parameters:

- `budget_cents` (integer): Authorized task budget in cents.
- `buyer_email` (string, required): 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)

Output parameters:

- `flow` (object)

### `milewise.get_job_status` (~42 tokens)

Get Milewise Job Status

Check the status of a Milewise job created through the beta.

Input parameters:

- `job_id` (integer, required): Milewise job id returned by milewise.post_job.

### `milewise.review_job_proof` (~106 tokens)

Review Milewise Job Proof

Accept, reject, or dispute submitted operator proof before payment capture and payout release.

Input parameters:

- `decision` (string, required): Review decision for the proof packet.
- `job_id` (integer, required): 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.

### `milewise.list_operator_profiles` (~48 tokens)

List Operator Profiles

List public operator profiles with verification, proof quality, delivery, and completion signals.

Input parameters:

- `location` (string): Optional location filter.
- `service` (string): Optional service/category filter.

### `milewise.search_operator_capabilities` (~61 tokens)

Search Operator Capabilities

Search early operator supply by service and location without exposing private contact details.

Input parameters:

- `location` (string): Optional city, country, timezone, or service area.
- `service` (string): Service to match, such as verified calls or local proof.

### `milewise.search_services` (~213 tokens)

Search Service Catalog

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.

Input parameters:

- `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.

### `milewise.get_marketplace_policy` (~28 tokens)

Get Marketplace Policy

Return Milewise's allowed task categories, disallowed work, and payment model.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-milewiseai-milewise/milewiseai#diagnostics

## Score history

- 2026-09-20: 73
- 2026-09-19: 73
- 2026-09-18: 72
- 2026-09-17: 72
- 2026-09-16: 71
- 2026-09-15: 71
- 2026-09-14: 70
- 2026-09-13: 70
- 2026-09-12: 69
- 2026-09-11: 69
- 2026-09-10: 68
- 2026-09-09: 68
- 2026-09-08: 67
- 2026-09-07: 67
- 2026-09-06: 66
- 2026-09-05: 66

## Common questions

### 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.

## Links

- Remote endpoint: https://milewiseai.com/mcp
- Authorisation metadata: https://milewiseai.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/beshogun/milewiseai
- Website: https://milewiseai.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-milewiseai-milewise/milewiseai.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-milewiseai-milewise/milewiseai.json
- HTML version of this page: https://verifymcp.io/servers/com-milewiseai-milewise/milewiseai