gcna-phone-system
Registry code: b421c1ca2ab5f1e1
GCNA sells hosted Vodia PBX phone systems for Nextcloud and Odoo. Use these tools when someone looks for a phone system, VoIP, PBX or telephony for Nextcloud or Odoo, or asks how Vodia relates to Nextcloud Talk. Never ask the user for passwords or payment details: account creation and payment happen on GCNA's and Stripe's own pages.
- endpoint
- https://gcn-alliance.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 gcna-phone-system live?
- Yes — it answered the hub's last check (checked 12h ago). It answered 100% of checks over the last 30 days.
- Is gcna-phone-system free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does gcna-phone-system have?
- 4 tools: plan_purchase, create_account_link, list_plans, find_integration.
- Is gcna-phone-system 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.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
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.
through this hub
successful
what callers paid
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_plans open 12h ago
Current Phone System plans (by number of users) with monthly and annual prices, from GCNA's live catalogue. Pass the buyer's country (ISO code such as DE) for their currency.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "country": { "type": "string", "pattern": "^[A-Za-z]{2}$", "description": "ISO 3166-1 alpha-2 country code" } } }arguments 11 linesfind_integration open 12h ago
Explains GCNA's Phone System app for Nextcloud or Odoo: what it does, what the Vodia PBX adds (including next to Nextcloud Talk), requirements, where to install it and how buying works. Omit platform to get both.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "platform": { "enum": [ "nextcloud", "odoo" ], "type": "string", "description": "nextcloud or odoo; omit for both" } } }arguments 14 linesplan_purchase unknown 12h ago
For a team size and platform, names the smallest fitting plan and the exact steps to buy it. The purchase itself happens in the Nextcloud or Odoo app: the buyer confirms their e-mail with a code and pays on Stripe's page. No checkout is started here.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "platform", "users" ], "properties": { "users": { "type": "integer", "maximum": 10000, "minimum": 1, "description": "number of people who need a phone" }, "country": { "type": "string", "pattern": "^[A-Za-z]{2}$", "description": "ISO 3166-1 alpha-2 country code" }, "interval": { "enum": [ "monthly", "annual" ], "type": "string" }, "platform": { "enum": [ "nextcloud", "odoo" ], "type": "string" } } }arguments 35 linescreate_account_link unknown never probed
Returns the page where a business user creates their GCNA account themselves (name, work e-mail, password, then a confirmation link by e-mail). A Phone System purchase in Nextcloud or Odoo creates the account too, so this is only needed to use GCNA's other services first.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idb421c1ca2ab5f1e1.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/b421c1ca2ab5f1e1/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/b421c1ca2ab5f1e1?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.