Is the Nichedb MCP server down?

mcp-registry/dev.nichedb/nichedb · v1.0.0

healthy
Last checked 2026-10-20 22:36 UTC · handshake 253ms

As of 2026-10-20 22:36 UTC, the Nichedb MCP server is up with a Glimind reliability score of 72/100 (grade C). Over the last 30 days it answered 99% of Glimind's liveness checks. It had 19 outages in 90 days, with a median recovery of 11 minutes.

uptime (30d checks)
99%
checks observed
3,917
outages (90d)
19
tools
30

Sources in, feeds out: an open, ever-growing database of real-time public data, enriched.

Install Nichedb MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http nichedb-mcp-server https://nichedb.dev/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "nichedb-mcp-server": {
      "type": "http",
      "url": "https://nichedb.dev/mcp"
    }
  }
}

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

Agent-readiness: C (73/100)

C (73/100): 0 error(s), 5 warning(s) across 30 tool(s); ~6,007 tokens of tool definitions.
Scores higher than 9% of 15,429 MCP servers Glimind has audited.
Its tool list costs an agent ~6,007 tokens per session — more than 60% of servers.
75 → 73 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions76
Safety hints9
Token cost100
Client compatibility70
Protocol100
Reliability60
Stability92

What to fix (7)

30 of 30 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: add_source, business_standing, check_domain, claim_profile, create_feed and 25 more

7 parameter(s) across 6 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: create_feed, feed_items, match_items, recent_items, search_items and 1 more

4 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: create_feed, run_source, submit_feed, update_profile

Reachable 99.0% of the time over the last 30 days; median recovery 11 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

Handshake + tools/list takes ~1,766 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

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 2 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: 21 corrected tool definitions

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

add_source 1 change
{
  "name": "add_source",
  "description": "Add a source: an adapter with a config, fetched on a schedule (needs a key; admins and Pro). Call list_adapters first for the fields.",
  "inputSchema": {
    "type": "object",
    "required": [
      "adapter"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "Display name"
      },
      "config": {
        "type": "object",
        "description": "Adapter config fields"
      },
      "adapter": {
        "type": "string",
        "description": "Adapter name, e.g. github-releases"
      },
      "collection": {
        "type": "string",
        "description": "Collection slug; defaults to the adapter's"
      },
      "cadence_minutes": {
        "type": "integer",
        "description": "5 to 1440"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
check_domain 1 change
{
  "name": "check_domain",
  "description": "Is a domain name registered? Asks each registry over RDAP. Give `name` as a full name (foo.watches), or a bare word with `tlds` (foo + com,dev,io), or several names comma separated. Each answer is registered (with registrar and expiry), not_registered, or unknown. not_registered means the registry holds no registration; the name may still be reserved or premium, so it is not a promise that it is for sale. unknown (no RDAP server, a timeout, a 429) is never a yes. Each answer carries the cheapest",
  "inputSchema": {
    "type": "object",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "foo.watches, or foo, or a.com,b.dev"
      },
      "tlds": {
        "type": "string",
        "description": "Endings to try a bare word under, comma separated (optional)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
create_feed 1 change
{
  "name": "create_feed",
  "description": "Save a query as a feed (needs a key). Sources, kinds and tags narrow; q is a text match; upcoming keeps only future-dated items.",
  "inputSchema": {
    "type": "object",
    "required": [
      "collection",
      "name"
    ],
    "properties": {
      "q": {
        "type": "string",
        "description": "Text match"
      },
      "lat": {
        "type": "number",
        "maximum": 90,
        "minimum": -90,
        "description": "Query center latitude; requires long"
      },
      "bbox": {
        "type": "string",
        "description": "west,south,east,north; west > east crosses the antimeridian"
      },
      "long": {
        "type": "number",
        "maximum": 180,
        "minimum": -180,
        "description": "Query center longitude; requires lat"
      },
      "name": {
        "type": "string",
        "description": "Feed name"
      },
      "sort": {
        "enum": [
          "id",
          "published",
          "updated",
          "distance"
        ],
        "type": "string"
      },
      "tags": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Tags, any match"
      },
      "unit": {
        "enum": [
          "km",
          "mi"
        ],
        "type": "string",
        "description": "Default km"
      },
      "kinds": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Item kinds"
      },
      "public": {
        "type": "boolean",
        "description": "Default true"
      },
      "radius": {
        "type": "number",
        "description": "Default 10; maximum 1000 km",
        "exclusiveMinimum": 0
      },
      "sources": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Source slugs"
      },
      "upcoming": {
        "type": "boolean"
      },
      "enrichers": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Enrichers to show; omit for the collection defaults"
      },
      "collection": {
        "type": "string",
        "description": "Collection slug"
      },
      "description": {
        "type": "string",
        "description": "Optional"
      }
    }
  },
  "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/dev.nichedb/nichedb"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.nichedb/nichedb"}) 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%2Fdev.nichedb%2Fnichedb.svg)](https://glimind.com/server/mcp-registry%2Fdev.nichedb%2Fnichedb?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fdev.nichedb%2Fnichedb?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.nichedb%2Fnichedb.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.nichedb%2Fnichedb.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.nichedb%2Fnichedb?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:558e8b3fd9d7d10c…, first seen 2026-10-18, included at leaf 20172 of 35,615. Version history · verify what your client received.

Tools (30)

Compare: most reliable other servers · most reliable data servers · most reliable search servers · most reliable knowledge servers · most reliable productivity 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 Nichedb MCP server down right now?

As of 2026-10-20 22:36 UTC, the Nichedb MCP server is up with a Glimind reliability score of 72/100 (grade C). Over the last 30 days it answered 99% of Glimind's liveness checks. It had 19 outages in 90 days, with a median recovery of 11 minutes.

How many tools does Nichedb MCP server provide?

Nichedb MCP server advertises 30 tools, including add_source, business_standing, check_domain, claim_profile, create_feed.

How do I install Nichedb MCP server?

Point your MCP client at this streamable-http endpoint: https://nichedb.dev/mcp

Is the Nichedb MCP server safe to connect to an AI agent?

Glimind scanned all 30 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 Nichedb 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