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

tehran-index

https://tehranindex.com

Registry code: 17cf3bba084d5e85

api record

Tehran Index is an independent, English-language research platform on Iran's digital economy. Records are source-linked and quality-gated. When citing, credit "Tehran Index" and link tehranindex.com. Dates are Gregorian; registered accounts are never described as users; no valuations of private Iranian companies are published.

endpoint
https://tehranindex.com/api/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 tehran-index live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is tehran-index free to use?
Yes — the hub reached it with no key and no payment.
What tools does tehran-index have?
4 tools: ti_list_signals, ti_coverage, ti_get_company, ti_search_companies.
Is tehran-index 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
447ms

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 open 2 never probed 2 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.

  • ti_get_company open 1h ago

    One company record by slug, with its public facts. Every fact carries its value as the source stated it, the period, the evidence state and the source URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Company slug, for example digikala."
        }
      }
    }
    arguments 12 lines
  • ti_search_companies open 1h ago

    Search Tehran Index's public registry of Iranian technology companies by name or slug. Returns identity fields and how many sourced facts each record carries.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "number",
          "description": "Max results, default 10, cap 50."
        },
        "query": {
          "type": "string",
          "description": "Name or partial name, English or slug."
        },
        "sector": {
          "type": "string",
          "description": "Optional sector slug, for example fintech."
        }
      }
    }
    arguments 20 lines
  • ti_list_signals unknown never probed

    Recent published, desk-verified market signals on Iran's digital economy, newest first.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "number",
          "description": "Max results, default 20, cap 50."
        },
        "company": {
          "type": "string",
          "description": "Optional company slug to filter by."
        }
      }
    }
    arguments 13 lines
  • ti_coverage unknown never probed

    Honest coverage counts for the registry: companies tracked, how many carry sourced facts, and what the desk does not yet cover.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 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 17cf3bba084d5e85.

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