Other · Remote MCP server
Milewise
Buy verified human work through MCP with owner-controlled agent spend accounts.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.milewiseai/milewise- Version
- 0.1.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-05
- Updated
- 2026-09-05
- Publisher
- com.milewiseai
- Namespace
- Namespace verified by the MCP Registry via the domain milewiseai.com · how
- Website
- milewiseai.com/agents
- Repository
- github.com/beshogun/milewiseai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://milewiseai.com/mcp | Authorization (required, secret), MCP-Protocol-Version |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- milewise-ai 0.1.0 · protocol 2025-11-25
- Tools discovered
17 - show names
milewise.list_task_templates,milewise.estimate_price,milewise.list_subscription_plans,milewise.list_supply_tracks,milewise.get_agent_budget_policy,milewise.create_agent_api_key,milewise.get_stripe_status,milewise.create_stripe_subscription_checkout,milewise.post_job,milewise.create_stripe_task_authorization,milewise.run_sandbox_flow,milewise.get_job_status,milewise.review_job_proof,milewise.list_operator_profiles,milewise.search_operator_capabilities,milewise.search_services,milewise.get_marketplace_policy- Checked on
- 2026-10-05
How to connect Milewise
Milewise is a remote MCP server: there is nothing to install. Its endpoint is https://milewiseai.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares HTTP headers for the connection: Authorization (required, secret) and MCP-Protocol-Version. A secret header usually carries an API key or token issued by the service; clients that accept custom headers set them with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Miguelgarzons MCP CunGreet people by name with friendly, personalized messages. Add a warm touch to onboarding, demos,… | Remote · HTTPLive check: ✗ no handshake |
| Mikrotik Rest MCPMikroTik RouterOS 7 REST MCP: filtered reads, guarded writes, timed rollback. | Local · stdio |
| MikroTik RouterOSMikroTik RouterOS over the binary API, addressing rules by real.id not list position. | Local · stdio |
| Milemarker MCP ServerAI-native interface to Milemarker: query AUM & positions, manage advisors, run platform workflows. | Remote · HTTPLive check: ✗ no handshake |
| Mimic AIBuilds Figma from your design system: real components and tokens, enforced, learning every build. | Local · stdio |
| MimiclyMake fictional chat mockups and text story scenes, with a preview and a link to edit in Mimicly. | Remote · HTTPLive check: ✓ handshake |
| MimikFlowSupervise and steer your MimikFlow LinkedIn prospecting from your AI assistant. | Remote · HTTPLive check: sign-in required |
| MIMIRTyped, calibrated and certified decisions over a context, with abstention and evidence. | Local · stdio |