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

GospelChannel Church Finder

https://gospelchannel.com

Registry code: 3cd8b301c6daf836

api record

GospelChannel, The Church Guide, helps someone find a Christian church that fits them – especially when they are new in a place or traveling. Lead with fit: worship style (contemporary, gospel, charismatic, traditional), denomination, language, and location. Call find_churches_near for the user's current area only when ChatGPT shares coarse location metadata. Call find_churches_in_city when the user explicitly names a destination city. Service times are shown only when recorded and may be stale – always tell the user to confirm with the church, and never invent a time. Link people to each…

endpoint
https://gospelchannel.com/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 GospelChannel Church Finder live?
Yes — it answered the hub's last check (checked 51m ago). It answered 100% of checks over the last 30 days.
Is GospelChannel Church Finder free to use?
Yes — the hub reached it with no key and no payment.
What tools does GospelChannel Church Finder have?
3 tools: find_churches_in_city, find_churches_near, get_church.
Is GospelChannel Church Finder 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 99.3%· all time 99.3%

latency
780ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 281 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
maps travel & places places & venues
used for
  • find churches in a city
  • find churches near the user
  • get a church's profile and service times
takes → gives
text → data
tools
3 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 3 tools
3 never probed 0 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.

  • find_churches_in_city reads unknown 51m ago

    Find Christian worship churches in a named city, ranked by directory quality. Filter by worship style, denomination, or language.

    mcp-tool

    {
  "type": "object",
  "required": [
    "city"
  ],
  "properties": {
    "city": {
      "type": "string",
      "description": "A destination city explicitly named by the user, e.g. Austin, Barcelona, London. A trailing region or country is accepted."
    },
    "limit": {
      "type": "number",
      "description": "Maximum number of churches to return (default 8, max 20)."
    },
    "language": {
      "type": "string",
      "description": "Preferred service language, e.g. English, Spanish."
    },
    "denomination": {
      "type": "string",
      "description": "Preferred denomination, e.g. non-denominational, Baptist, Pentecostal."
    },
    "worship_style": {
      "type": "string",
      "description": "Preferred worship style, e.g. contemporary, gospel, charismatic, traditional, hillsong."
    }
  }
}
    arguments 28 lines
  • find_churches_near reads unknown 51m ago

    Find Christian worship churches near the user, ranked by distance. Uses only the coarse location metadata ChatGPT shares, never raw location input fields. If the metadata includes only a city, it searches that city. Filter by worship style, denomination, or language.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Maximum number of churches to return (default 5, max 20)."
    },
    "language": {
      "type": "string",
      "description": "Preferred service language, e.g. English, Spanish."
    },
    "radius_km": {
      "type": "number",
      "description": "Search radius in kilometers (default 40, max 500)."
    },
    "denomination": {
      "type": "string",
      "description": "Preferred denomination, e.g. non-denominational, Baptist, Pentecostal, Assemblies of God."
    },
    "worship_style": {
      "type": "string",
      "description": "Preferred worship style, e.g. contemporary, gospel, charismatic, traditional, hillsong."
    }
  }
}
    arguments 25 lines
  • get_church reads unknown 51m ago

    Get the full profile for one church by its slug (the last path segment of its gospelchannel.com/church/<slug> URL): worship styles, denomination, language, summary, top worship songs, contact, and recorded service times if available.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "The church slug, e.g. hillsong-church-london."
    }
  }
}
    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 3cd8b301c6daf836.

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