mcp-registry/com.nikhilkulkarni1755/iridium · v1.28.1
As of 2026-10-24 17:38 UTC, the Nikhilkulkarni1755 Iridium MCP server is up (it requires sign-in) with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 2 minutes.
LinkedIn outreach, commenting, scheduling, and data via Claude and human approval gates.
Claude Code
claude mcp add --transport http nikhilkulkarni1755-iridium-mcp-server https://iridium-api.nikhilkulkarni1755.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"nikhilkulkarni1755-iridium-mcp-server": {
"type": "http",
"url": "https://iridium-api.nikhilkulkarni1755.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
42 of 42 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 →
42 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 →
75 parameter(s) across 27 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 →
12 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 →
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 →
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 27 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.nikhilkulkarni1755%2Firidium/fixes
{
"name": "approve_comment_draft",
"description": "Approve Comment Draft\n\n### Responses:\n\n**200**: Successful Response (Success Response)\nContent-Type: application/json",
"inputSchema": {
"type": "object",
"title": "approve_comment_draftArguments",
"required": [
"handle"
],
"properties": {
"handle": {
"type": "string",
"title": "handle"
},
"comment_at": {
"type": "string",
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "comment_at"
},
"comment_text": {
"type": "string",
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "comment_text"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "approve_content_draft",
"description": "Approve Content Draft\n\n### Responses:\n\n**200**: Successful Response (Success Response)\nContent-Type: application/json",
"inputSchema": {
"type": "object",
"title": "approve_content_draftArguments",
"required": [
"handle",
"post_text"
],
"properties": {
"handle": {
"type": "string",
"title": "handle"
},
"post_text": {
"type": "string",
"title": "post_text"
},
"scheduled_at": {
"type": "string",
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "scheduled_at"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "approve_draft",
"description": "Approve Draft\n\n### Responses:\n\n**200**: Successful Response (Success Response)\nContent-Type: application/json",
"inputSchema": {
"type": "object",
"title": "approve_draftArguments",
"required": [
"handle"
],
"properties": {
"handle": {
"type": "string",
"title": "handle"
},
"override_text": {
"type": "string",
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "override_text"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}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/com.nikhilkulkarni1755/iridium"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.nikhilkulkarni1755/iridium"}) over MCP.
update_settings ~461 tokensget_linkedin_profile ~389 tokensrun_company_commenting_pipeline ~250 tokensschedule_manual_dm ~248 tokensdiscover_prospects ~228 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%2Fcom.nikhilkulkarni1755%2Firidium?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.nikhilkulkarni1755%2Firidium?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.nikhilkulkarni1755%2Firidium.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.nikhilkulkarni1755%2Firidium.svg :target: https://glimind.com/server/mcp-registry%2Fcom.nikhilkulkarni1755%2Firidium?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:4233ff573d7f8c7d…, first seen 2026-10-17, included at leaf 9757 of 60,211. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable sales servers · most reliable security servers · most reliable other servers · most reliable search 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-24 17:38 UTC, the Nikhilkulkarni1755 Iridium MCP server is up (it requires sign-in) with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 2 minutes.
Nikhilkulkarni1755 Iridium MCP server advertises 42 tools, including approve_comment_draft, approve_content_draft, approve_draft, backfill_chats, cancel_scheduled.
Point your MCP client at this streamable-http endpoint: https://iridium-api.nikhilkulkarni1755.com/mcp
Glimind scanned all 42 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.