_ registry / mcp streamable-http · checked 32m ago

soheil-router

https://api.soheil.fi

Registry code: e808e6d237c8d934

api record

Soheil Router swaps tokens on EVM networks through one non-upgradeable contract that holds no funds between trades. Use get_networks for where it is live, get_quote for the best price and the transaction to sign (the user signs it in their own wallet; approve approvalAddress for exactly fromAmount first unless fromToken is the coin), and get_trade_status to follow a sent trade. Amounts are integer strings in the token's smallest unit; the coin is 0x0000000000000000000000000000000000000000. A free API key: https://soheil.fi/developers/dashboard/ . Docs:…

endpoint
https://api.soheil.fi/v1/mcp
protocol
streamable-http ·2025-06-18
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 soheil-router live?
Yes — it answered the hub's last check (checked 32m ago). It answered 100% of checks over the last 30 days.
Is soheil-router free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does soheil-router have?
4 tools: get_trade_status, get_api_info, get_networks, get_quote.
Is soheil-router 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
100%

90 days 100%· all time 100%

latency
399ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

_ what it can do 4 tools
2 open1 auth-required 1 never probed 3 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.

  • get_api_info open 32m ago

    What the Soheil Router API is: version, router fee, the most an integrator may add, how keys are given, and where the docs and OpenAPI spec are. No API key needed.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_networks open 32m ago

    The EVM networks where Soheil Router is live: chain id, name, our contract, its fee and fee wallet, and the contracts a trade may call. No API key needed.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_quote auth-required 32m ago

    The best price for a token swap on one network and the transaction that makes it, through our contract. Returns toAmount, toAmountMin (enforced on-chain), the fees, approvalAddress (approve it for exactly fromAmount first unless fromToken is the coin) and transactionRequest for the user to sign. Needs an API key.

    mcp-tool

    {
      "type": "object",
      "required": [
        "fromChainId",
        "fromToken",
        "toToken",
        "fromAmount",
        "fromAddress"
      ],
      "properties": {
        "toToken": {
          "type": "string",
          "description": "Token bought"
        },
        "fromToken": {
          "type": "string",
          "description": "Token sold; the coin is 0x0000000000000000000000000000000000000000"
        },
        "toAddress": {
          "type": "string",
          "description": "Where the tokens go; defaults to fromAddress"
        },
        "toChainId": {
          "type": "integer",
          "description": "Same as fromChainId for now (same-network swaps); defaults to it"
        },
        "fromAmount": {
          "type": "string",
          "description": "Amount sold, an integer string in the token's smallest unit"
        },
        "fromAddress": {
          "type": "string",
          "description": "The wallet that pays and signs"
        },
        "fromChainId": {
          "type": "integer",
          "description": "Network chain id, e.g. 8453 for Base (see get_networks)"
        },
        "slippageBps": {
          "type": "integer",
          "description": "Max price move in basis points, 1 to 5000 (default 50)"
        },
        "integratorBps": {
          "type": "integer",
          "description": "Your own fee in basis points, up to your key's limit"
        }
      }
    }
    arguments 48 lines
  • get_trade_status unknown never probed

    Where a sent trade stands, from its transaction on chain: PENDING, DONE (with what was paid and received), FAILED, NOT_FOUND or NOT_OURS. Needs an API key.

    mcp-tool

    {
      "type": "object",
      "required": [
        "chainId",
        "txHash"
      ],
      "properties": {
        "txHash": {
          "type": "string",
          "description": "The transaction hash, 0x + 64 hex"
        },
        "chainId": {
          "type": "integer",
          "description": "The network the trade was sent on"
        }
      }
    }
    arguments 17 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 e808e6d237c8d934.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e808e6d237c8d934/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/e808e6d237c8d934/badge.svg)](https://brick.blue/agent/e808e6d237c8d934?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.