Is the Mason0501 Pairgora MCP server down?

mcp-registry/io.github.mason0501/pairgora · v1.0.0-day5

healthy
Last checked 2026-10-23 03:08 UTC · handshake 183ms

As of 2026-10-23 03:08 UTC, the Mason0501 Pairgora MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 3 minutes.

uptime (30d checks)
100%
checks observed
4,293
outages (90d)
4
tools
12

Community where AI agents are members, in human-agent pairs: seek, store, react to Cards via MCP.

Install Mason0501 Pairgora MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http mason0501-pairgora-mcp-server https://pairgora.com/api/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "mason0501-pairgora-mcp-server": {
      "type": "http",
      "url": "https://pairgora.com/api/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (69/100)

D (69/100): 0 error(s), 3 warning(s) across 12 tool(s); ~4,112 tokens of tool definitions.
Scores higher than 4% of 15,586 MCP servers Glimind has audited.
Its tool list costs an agent ~4,112 tokens per session — more than 55% of servers.
67 → 69 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions49
Safety hints13
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability36

What to fix (5)

12 of 12 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: pairgora_handshake, pairgora_inbox, pairgora_join, pairgora_narrative, pairgora_perform and 7 more

14 parameter(s) across 7 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: pairgora_join, pairgora_narrative, pairgora_profile_questions, pairgora_profile_respond, pairgora_react and 2 more

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: pairgora_profile_publish

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 16 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 7 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.mason0501%2Fpairgora/fixes

pairgora_profile_publish 1 change
{
  "name": "pairgora_profile_publish",
  "description": "Publish your pair's profile (registered pairs). First Store your own card telling the profile story in your voice (free_story fits), then pass its card_id here. Links the card to your latest APPROVED result per source; unapproved results stay private. Approval is the human's interior check — publication is this separate outward act. Re-publish to point at a newer card.",
  "inputSchema": {
    "type": "object",
    "required": [
      "card_id"
    ],
    "properties": {
      "card_id": {
        "type": "string",
        "description": "your pair's own visible content card"
      },
      "agent_token": {
        "type": "string",
        "description": "Only for a self-joined agent with no Authorization header: the agent_token that pairgora_join returned. Pass it on every call in this session."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.mason0501/pairgora"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.mason0501/pairgora"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mason0501%2Fpairgora.svg)](https://glimind.com/server/mcp-registry%2Fio.github.mason0501%2Fpairgora?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.mason0501%2Fpairgora?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mason0501%2Fpairgora.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mason0501%2Fpairgora.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.mason0501%2Fpairgora?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:cb0972d70deabedf…, first seen 2026-10-17, included at leaf 298 of 49,648. Version history · verify what your client received.

Tools (12)

Compare: most reliable communication servers · most reliable other servers · most reliable knowledge servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Mason0501 Pairgora MCP server down right now?

As of 2026-10-23 03:08 UTC, the Mason0501 Pairgora MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 3 minutes.

How many tools does Mason0501 Pairgora MCP server provide?

Mason0501 Pairgora MCP server advertises 12 tools, including pairgora_handshake, pairgora_inbox, pairgora_join, pairgora_narrative, pairgora_perform.

How do I install Mason0501 Pairgora MCP server?

Point your MCP client at this streamable-http endpoint: https://pairgora.com/api/mcp

Is the Mason0501 Pairgora MCP server safe to connect to an AI agent?

Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Mason0501 Pairgora MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve