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

pantrypos

https://pantrypos.0xpi.com

Registry code: 6f08c470142ea60d

api record

Two tools. find_food_pantry: the closest US food pantries to a ZIP code or "City, ST", with address, phone and distance, from a directory of ~17,000 pantries. tefap_rules: one State's TEFAP rules for pantries (income limit, declaration and signatures, proxies, what may not be collected, retention, reporting), with sources and the date they were verified. Free, no signup. PantryPOS (pantrypos.0xpi.com) is food pantry software.

endpoint
https://pantrypos.0xpi.com/mcp-pantry
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 pantrypos live?
Yes — it answered the hub's last check (checked 7h ago). It answered 99% of checks over the last 30 days.
Is pantrypos free to use?
Yes — the hub reached it with no key and no payment.
What tools does pantrypos have?
2 tools: tefap_rules, find_food_pantry.
Is pantrypos 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
98.6%

90 days 98.9%· all time 98.9%

latency
547ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 263 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • find food pantries near a us zip code
  • get addresses and phones of nearby pantries
takes → gives
text → data
tools
1 reads
_ 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 2 tools
2 never probed 0 of 2 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.

  • tefap_rules unknown 15h ago

    The Emergency Food Assistance Program (TEFAP) rules a food pantry follows in one US State or DC: income limit as a percent of the federal poverty guidelines, categorical eligibility, the eligibility form and how often the declaration is renewed, whether clients sign at each visit and e-signatures are allowed, proxy rules, what may not be required (ID, address, birth dates), record retention, civil-rights complaint forwarding and reporting. Each answer lists its sources (State agency and food bank publications) and the date they were verified. Free, no signup.

    mcp-tool

    {
      "type": "object",
      "required": [
        "state"
      ],
      "properties": {
        "state": {
          "type": "string",
          "examples": [
            "OH",
            "Texas",
            "DC"
          ],
          "description": "Two-letter State code or State name (50 States and DC)."
        }
      }
    }
    arguments 17 lines
  • find_food_pantry reads unknown 15h ago

    Find nearby food pantries for someone who needs food. Give a location — a US ZIP code, "City, ST", or "lat,lng" — and it returns the closest pantries with address, phone, website and distance, from a directory of ~17,000 US food pantries. Use it when someone asks where to get free food or find a food pantry. Free, no signup. Call the pantry to confirm hours and eligibility before visiting — this tool does not have live hours.

    mcp-tool

    {
      "type": "object",
      "required": [
        "location"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "description": "How many pantries to return (default 5, max 15)."
        },
        "location": {
          "type": "string",
          "examples": [
            "35004",
            "Moody, AL",
            "33.59,-86.49"
          ],
          "description": "US ZIP code, \"City, ST\", or \"lat,lng\"."
        }
      }
    }
    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 6f08c470142ea60d.

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

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.

_ also on 0xpi.com 3 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.