mcp-registry/dev.nichedb/nichedb · v1.0.0
As of 2026-10-26 22:34 UTC, the Nichedb MCP server is up with a Glimind reliability score of 76/100 (grade B). Over the last 30 days it answered 99.3% of Glimind's liveness checks. It had 22 outages in 90 days, with a median recovery of 8 minutes.
Sources in, feeds out: an open, ever-growing database of real-time public data, enriched.
Point your MCP client at this streamable-http endpoint: https://nichedb.dev/mcp
34 of 34 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 →
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 →
6 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 →
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 →
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
{
"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
}
}{
"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
}
}{
"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 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.
search_tlds ~491 tokensmatch_items ~452 tokenscreate_feed ~408 tokensupdate_profile ~408 tokenssearch_profiles ~355 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%2Fdev.nichedb%2Fnichedb?ref=badge)
<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>
.. 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
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7f1f0104f6ce4428…, first seen 2026-10-26, included at leaf 74346 of 75,853. Version history · verify what your client received.
Compare: most reliable other servers · most reliable data servers · most reliable search servers · most reliable knowledge servers · most reliable productivity 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 22:34 UTC, the Nichedb MCP server is up with a Glimind reliability score of 76/100 (grade B). Over the last 30 days it answered 99.3% of Glimind's liveness checks. It had 22 outages in 90 days, with a median recovery of 8 minutes.
Nichedb MCP server advertises 34 tools, including add_source, business_standing, check_domain, claim_profile, create_feed.
Point your MCP client at this streamable-http endpoint: https://nichedb.dev/mcp
Glimind scanned all 34 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.