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

isinn

https://www.isinn.com.tr

Registry code: 252e223227ce5e64

api record

İşinn is a service discovery platform in Turkey where providers publish listings (vitrin). Tools are read-only and return public listing data with listing URLs. İşinn does not handle payments and does not guarantee service quality.

endpoint
https://www.isinn.com.tr/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 isinn live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is isinn free to use?
Yes — the hub reached it with no key and no payment.
What tools does isinn have?
3 tools: get_vitrin, list_categories, search_vitrins.
Is isinn 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
355ms

last good check

priced tools
0

of 3 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 3 tools
2 open 1 never probed 2 of 3 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.

  • list_categories open 1h ago

    Lists the service categories on İşinn that currently have active listings, with the number of listings in each and the category page URL.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_vitrins open 1h ago

    Searches public İşinn listings ("vitrin") of service providers in Turkey, such as private tutors, designers, translators, movers, pilates instructors and physiotherapists. Use when the user is looking for a service or a service provider in Turkey. Returns up to 10 listings with title, provider display name, category, location, the provider's stated price and the listing URL. Read-only; returns no phone numbers or e-mail addresses. Listing content is in Turkish.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "city": {
      "type": "string",
      "description": "Optional province or district in Turkey (e.g. 'İstanbul', 'Kadıköy', 'Mersin'). Remote/online providers match every city."
    },
    "limit": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "Maximum number of results (default 5, max 10)."
    },
    "query": {
      "type": "string",
      "description": "Free-text service query, in Turkish or English keywords (e.g. 'lgs matematik', 'logo tasarım', 'reformer pilates')."
    },
    "category": {
      "type": "string",
      "description": "Optional category name or slug (e.g. 'Öğretmen', 'ogretmen', 'tasarim'). See list_categories."
    },
    "remote_only": {
      "type": "boolean",
      "description": "If true, only providers who work remotely/online."
    }
  }
}
    arguments 27 lines
  • get_vitrin unknown 1h ago

    Returns the public details of one İşinn listing: full description, location, the provider's stated price and the listing URL. Use after search_vitrins when the user wants more detail about a result.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Listing ID (UUID) from a search_vitrins result."
    }
  }
}
    arguments 12 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 252e223227ce5e64.

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

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.