_ registry / mcp streamable-http · checked 1h ago

MyRouteOnline MCP Server

https://planner.myrouteonline.com

Registry code: ea833085b2c87124

api record

Multi-stop route optimization, navigation links, and email delivery. Powered by MyRouteOnline.

from a public catalogue that lists it, not from the operator

endpoint
https://planner.myrouteonline.com/ws_api_ai/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is MyRouteOnline MCP Server live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is MyRouteOnline MCP Server free to use?
Yes — the hub reached it with no key and no payment.
What tools does MyRouteOnline MCP Server have?
4 tools: getOneTimeCode, checkOptimization, startOptimization, emailResults.
Is MyRouteOnline MCP Server safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 99.7%· all time 99.7%

latency
619ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 326 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • optimize a multi-stop delivery route
  • get navigation links for a route
  • email optimized route results
takes → gives
text, data → data
tools
1 reads1 changes data2 sends messages
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • getOneTimeCode sends messages unknown 5h ago

    Request a one-time authentication code to be sent via email. This code is required for all other operations.

    mcp-tool

    {
      "type": "object",
      "required": [
        "loginEmail"
      ],
      "properties": {
        "loginEmail": {
          "type": "string",
          "format": "email",
          "description": "Email address to receive the one-time code"
        }
      }
    }
    arguments 13 lines
  • checkOptimization reads unknown 5h ago

    Check the status and results of a route optimization job. Returns the optimized route when complete. Authenticate with either (otpCode + otpEmail) or mroApiKey.

    mcp-tool

    {
      "type": "object",
      "required": [
        "jobToken"
      ],
      "properties": {
        "otpCode": {
          "type": "string",
          "description": "6-digit one-time code (required if mroApiKey is not provided)"
        },
        "jobToken": {
          "type": "string",
          "description": "Job token returned from startOptimization"
        },
        "otpEmail": {
          "type": "string",
          "format": "email",
          "description": "Email address (required if mroApiKey is not provided)"
        },
        "mroApiKey": {
          "type": "string",
          "description": "MyRouteOnline API key (alternative to otpCode + otpEmail, obtained from MyRouteOnline support)"
        }
      }
    }
    arguments 25 lines
  • startOptimization changes data unknown never probed

    Start a route optimization job with multiple addresses. Authenticate with either (otpCode + otpEmail) or mroApiKey.

    mcp-tool

    {
      "type": "object",
      "required": [
        "addresses"
      ],
      "properties": {
        "otpCode": {
          "type": "string",
          "description": "6-digit one-time code received via email (required if mroApiKey is not provided)"
        },
        "otpEmail": {
          "type": "string",
          "format": "email",
          "description": "Email address that received the one-time code (required if mroApiKey is not provided)"
        },
        "addresses": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "address"
            ],
            "properties": {
              "title": {
                "type": "string",
                "description": "Location name/title"
              },
              "address": {
                "type": "string",
                "description": "Street address"
              },
              "comments": {
                "type": "string",
                "description": "Additional notes"
              }
            }
          },
          "description": "List of addresses to optimize (minimum 3)"
        },
        "mroApiKey": {
          "type": "string",
          "description": "MyRouteOnline API key (alternative to otpCode + otpEmail, obtained from MyRouteOnline support)"
        },
        "startTimeHHMM": {
          "type": "string",
          "description": "Start time in HH:MM format (default: 08:00)"
        }
      }
    }
    arguments 49 lines
  • emailResults sends messages unknown never probed

    Email the optimized route results with navigation links to a specified email address. Authenticate with either (otpCode + otpEmail) or mroApiKey.

    mcp-tool

    {
      "type": "object",
      "required": [
        "jobToken",
        "toEmail"
      ],
      "properties": {
        "otpCode": {
          "type": "string",
          "description": "6-digit one-time code (required if mroApiKey is not provided)"
        },
        "toEmail": {
          "type": "string",
          "format": "email",
          "description": "Recipient email address"
        },
        "jobToken": {
          "type": "string",
          "description": "Job token from completed optimization"
        },
        "otpEmail": {
          "type": "string",
          "format": "email",
          "description": "Email address (required if mroApiKey is not provided)"
        },
        "mroApiKey": {
          "type": "string",
          "description": "MyRouteOnline API key (alternative to otpCode + otpEmail, obtained from MyRouteOnline support)"
        }
      }
    }
    arguments 31 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ea833085b2c87124.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ea833085b2c87124/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ea833085b2c87124/badge.svg)](https://brick.blue/agent/ea833085b2c87124?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.