mcp-registry/io.github.earonesty/relin · v1.0.0
As of 2026-10-26 17:58 UTC, the Earonesty Relin MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Inspect webhook health, investigate delivery failures, configure sources, and replay events.
Point your MCP client at this streamable-http endpoint: https://relin.app/mcp
53 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
153 parameter(s) across 45 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 →
2 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 45 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.earonesty%2Frelin/fixes
{
"name": "send_message",
"description": "Send a webhook event from an outbound app to the specified customer. Requires the intended app, recipient, event type, and payload. Delivery can trigger actions at customer endpoints; an accepted message is not proof of delivery.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"appId",
"recipient",
"type"
],
"properties": {
"data": {
"type": "string"
},
"type": {
"type": "string",
"minLength": 1
},
"appId": {
"type": "string",
"minLength": 1
},
"messageId": {
"type": "string"
},
"recipient": {
"type": "string",
"minLength": 1
},
"idempotencyKey": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
},
"title": "Send Message"
}{
"name": "upsert_event_type",
"description": "Create or update an outbound event type and its description for customer webhook subscriptions.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"appId",
"eventType"
],
"properties": {
"appId": {
"type": "string",
"minLength": 1
},
"schema": {
"type": "string"
},
"eventType": {
"type": "string",
"minLength": 1
},
"description": {
"type": "string"
},
"examplePayload": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": true
},
"title": "Upsert Event Type"
}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.earonesty/relin"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.earonesty/relin"}) over MCP.
ensure_webhook_setup ~351 tokenscreate_portal_host ~263 tokenscreate_destination ~250 tokenslist_open_issues ~227 tokenscreate_alert_channel ~208 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fio.github.earonesty%2Frelin?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.earonesty%2Frelin?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.earonesty%2Frelin.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.earonesty%2Frelin.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.earonesty%2Frelin?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9d700bccc35f2911…, first seen 2026-10-17, included at leaf 3193 of 74,588. Version history · verify what your client received.
Compare: most reliable other servers · most reliable devops servers · most reliable security servers · most reliable communication servers · most reliable knowledge servers
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.
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"
}
}
}
As of 2026-10-26 17:58 UTC, the Earonesty Relin MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Earonesty Relin MCP server advertises 53 tools, including archive_source, cancel_queued_retries, check_portal_host, create_alert_channel, create_api_key.
Point your MCP client at this streamable-http endpoint: https://relin.app/mcp
Glimind scanned all 53 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.
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.