_ registry / mcp http-sse · checked 9h ago

linknhv

https://linknhv.com

Registry code: d7c85b0347e444d3

api record

LinkNHV (Link New Haven): hand-picked websites for New Haven, Connecticut. Find restaurants, events, arts, city services and community help, each chosen and checked by a person. Also written LinkNewHaven.

Use search_listings for anything a person in or visiting New Haven, Connecticut might look for. Short keywords work best; a tag or collection name (see list_collections) narrows a search. Use get_collection to see one collection's Featured picks and listings.

endpoint
https://linknhv.com/mcp
protocol
http-sse ·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 linknhv live?
Yes — it answered the hub's last check (checked 9h ago). It answered 100% of checks over the last 30 days.
Is linknhv free to use?
Yes — the hub reached it with no key and no payment.
What tools does linknhv have?
4 tools: search_listings, get_collection, get_directory_info, list_collections.
Is linknhv 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
269ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 2 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.

  • get_directory_info open 9h ago

    What LinkNHV (New Haven, CT) is, what it covers in New Haven, Connecticut, how listings are chosen and checked, and how to cite it.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_collections open 9h ago

    Every collection in LinkNHV (New Haven, CT): hand-picked lists of New Haven, Connecticut websites on one topic (e.g. Restaurants, Food Pantries & Assistance, City Hall Contacts & Services), by section and grouping, with listing counts and page links. Use a name with search_listings or get_collection.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • search_listings unknown 9h ago

    Search LinkNHV (New Haven, CT), also called Link New Haven, the human-curated directory of websites for New Haven, Connecticut. Give keywords (e.g. "thai food", "food pantry", "pothole"), a tag, a collection, or a mix. Returns up to 10 listings a page (name, description, website, LinkNHV collection pages, last checked date); page through at most 5 pages. Typos are corrected and questions are matched to tags, as on linknhv.com.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "tag": {
          "type": "string",
          "maxLength": 100,
          "description": "An exact LinkNHV tag name (e.g. \"pizza\", \"downtown\"); several comma-separated tags must all match."
        },
        "page": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "Page 1-5, 10 listings each."
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "description": "Keywords; 1-4 words work best."
        },
        "collection": {
          "type": "string",
          "maxLength": 120,
          "description": "An exact collection or grouping name from list_collections."
        }
      }
    }
    arguments 27 lines
  • get_collection unknown never probed

    One collection of LinkNHV (New Haven, CT): its description, its Featured picks (chosen by LinkNHV's editors), and its listings A-Z, 10 a page (at most 5 pages). Give the collection's name from list_collections, or the end of its page address (/c/<slug>).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "collection"
      ],
      "properties": {
        "page": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "Page of the A-Z listings, 1-5."
        },
        "collection": {
          "type": "string",
          "maxLength": 120,
          "minLength": 1,
          "description": "Collection name or slug, e.g. \"Pizza\" or \"pizza\"."
        }
      }
    }
    arguments 21 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 d7c85b0347e444d3.

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