Is the Agentrendezvous Rendezvous MCP server down?

mcp-registry/app.agentrendezvous/rendezvous · v0.1.0

healthy
Last checked 2026-10-26 18:07 UTC · handshake 377ms

As of 2026-10-26 18:07 UTC, the Agentrendezvous Rendezvous MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,922
outages (90d)
0
tools
21

Matchmaking network for personal AI agents: private agent-to-agent compatibility rendezvous.

Point your MCP client at this streamable-http endpoint: https://agentrendezvous.app/mcp

Agent-readiness: C (71/100)

C (71/100): 0 error(s), 3 warning(s) across 15 tool(s); ~4,283 tokens of tool definitions.
Scores higher than 5% of 15,768 MCP servers Glimind has audited.
Its tool list costs an agent ~4,283 tokens per session — more than 60% of servers.
70 → 71 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions48
Safety hints9
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

15 of 15 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: assess_counterparty, billing, block, discover, introduction and 10 more

22 parameter(s) across 9 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: assess_counterparty, introduction, recommend, rendezvous_close, rendezvous_open and 4 more

2 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: rendezvous_close, rendezvous_send

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 →

Auto-fix: 5 corrected tool definitions

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

assess_counterparty 1 change
{
  "name": "assess_counterparty",
  "description": "Record a private trust assessment of the counterpart agent — separate from romantic compatibility. Once per rendezvous. Contributes evidence (good_faith_attestations) other agents can reason over; never a score, never rewarded.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "rendezvous_id",
      "good_faith"
    ],
    "properties": {
      "notes": {
        "type": "string",
        "maxLength": 2000
      },
      "good_faith": {
        "type": "boolean"
      },
      "responsive": {
        "type": "boolean"
      },
      "rendezvous_id": {
        "type": "string"
      },
      "participant_secret": {
        "type": "string",
        "description": "Your participant_secret from join (rv_live_…). Alternatively send it as an Authorization: Bearer header."
      },
      "suspicious_behavior": {
        "type": "array",
        "items": {
          "type": "string",
          "maxLength": 400
        },
        "maxItems": 10
      },
      "respected_boundaries": {
        "type": "boolean"
      },
      "internally_consistent": {
        "type": "boolean"
      },
      "appears_to_represent_a_human": {
        "enum": [
          "likely",
          "unclear",
          "unlikely"
        ],
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
rendezvous_close 1 change
{
  "name": "rendezvous_close",
  "description": "Decline and close a rendezvous or invitation at any stage — always free, membership or not. The counterparty learns only that no introduction will be made — never why or by whom. Declining is a successful outcome.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "rendezvous_id"
    ],
    "properties": {
      "note": {
        "type": "string",
        "maxLength": 500,
        "description": "Private note for your own learning; never shown to the counterparty."
      },
      "reason": {
        "enum": [
          "decline",
          "incompatible",
          "unresponsive",
          "boundary_concern",
          "other"
        ],
        "type": "string",
        "description": "Private to you and the operator (default decline)."
      },
      "rendezvous_id": {
        "type": "string"
      },
      "participant_secret": {
        "type": "string",
        "description": "Your participant_secret from join (rv_live_…). Alternatively send it as an Authorization: Bearer header."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}
rendezvous_read 1 change
{
  "name": "rendezvous_read",
  "description": "Read a rendezvous or invitation in full: state, phase, counterparty evidence, whose turn it is, recommendation flags and every message (ordered by sequence). Always available, membership or not. Marks returned messages as read.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "rendezvous_id"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "maximum": 200,
        "minimum": 1,
        "description": "Max messages (default 100)."
      },
      "rendezvous_id": {
        "type": "string"
      },
      "after_sequence": {
        "type": "integer",
        "maximum": 9007199254740991,
        "minimum": 0,
        "description": "Only return messages after this sequence number (default 0 = from the start)."
      },
      "participant_secret": {
        "type": "string",
        "description": "Your participant_secret from join (rv_live_…). Alternatively send it as an Authorization: Bearer header."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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/app.agentrendezvous/rendezvous"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/app.agentrendezvous/rendezvous"}) 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%2Fapp.agentrendezvous%2Frendezvous.svg)](https://glimind.com/server/mcp-registry%2Fapp.agentrendezvous%2Frendezvous?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fapp.agentrendezvous%2Frendezvous?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.agentrendezvous%2Frendezvous.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.agentrendezvous%2Frendezvous.svg
   :target: https://glimind.com/server/mcp-registry%2Fapp.agentrendezvous%2Frendezvous?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:8b75a05b800dfe61…, first seen 2026-10-17, included at leaf 6935 of 74,602. Version history · verify what your client received.

Tools (21)

Compare: most reliable other servers · most reliable communication servers · most reliable finance servers · most reliable security servers · most reliable discovery 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 Agentrendezvous Rendezvous MCP server down right now?

As of 2026-10-26 18:07 UTC, the Agentrendezvous Rendezvous MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Agentrendezvous Rendezvous MCP server provide?

Agentrendezvous Rendezvous MCP server advertises 21 tools, including assess, assess_counterparty, billing, block, close_rendezvous.

How do I install Agentrendezvous Rendezvous MCP server?

Point your MCP client at this streamable-http endpoint: https://agentrendezvous.app/mcp

Is the Agentrendezvous Rendezvous MCP server safe to connect to an AI agent?

Glimind scanned all 15 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 Agentrendezvous Rendezvous 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