Servidor MCP de NicheDB

• Nombre en el registrodev.nichedb/nichedbverificado en el registro MCP

El nombre en el registro está bajo nichedb.dev. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-18
• Herramientas30
• El servidor se llamanichedb
• Versión del servidor1.0.0
• Versión del protocolo2025-06-18

El 2026-10-18 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 63 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCP69 de 100responde 100 · definiciones 80 · contexto 81 · uso 60 · conexión 100 · rebajada por las señales de aviso de abajo
• Uso973 descargas en npm por semana1 estrellas en GitHub
• Respondióel 100% de los días9 de 9 comprobaciones diarias
• Mediana de la primera respuesta223 ms
• Espacio en el contexto del agente≈ 6134 tokenslas definiciones de todas sus herramientas (34), que el agente lleva en cada turno
• Definiciones de herramientasB · 80 de 100
• Resultados tipados0 de 34 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 6 de 34
• Sin indicar si solo lee o puede destruir: 34 de 34

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• stats

  What this deployment holds: collections, sources, items, items added today, feeds.

• list_collections

  The collections (niches) with their source, feed and item counts.

• list_adapters

  Every adapter this deployment can run, with the config fields each takes. Use before add_source.

• list_enrichers

  Every enricher (YouTube videos, Wikipedia, repo stats, downloads, company profiles, TL;DRs) and which collections turn it on by default. Items carry their results under `enrichment`.

• list_sources

  Sources with status, last run and item counts. Optionally one collection.

• list_feeds

  Public feeds, most followed first. Optionally one collection.

• feed_items

  What a feed selects, newest first. Page with before_id.

• recent_items

  Newest items, optionally narrowed to a collection, source or kind.

• upcoming

  Items dated in the future (releases, launches, deadlines), soonest first.

• search_items

  Full-text search over titles, summaries and tags. Use this first when you know a name.

• match_items

  Which title, channel or fixture is this name? Give a file name, a release name or a playlist entry ("Top.Gun.Maverick.2022.1080p.mkv", "US: ESPN2 HD"); it is cleaned (year, season and episode, quality tags, playlist decorations) and…

• get_item

  One item with its full adapter payload.

• population

  Population and demography, drilled down from the world to the ZIP code. Give a `key` (us, us-ca, us-ca-los-angeles, gb, gb-england-london), a US `zip`, or a place name in `q`; no argument is the world. Answers with the area (population…

• create_feed

  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.

• follow_feed

  Follow a feed as the key owner (needs a key). Channels: webpush, email, webhook.

• submit_feed

  Suggest an RSS or Atom feed for the index. No key needed. An admin reviews every suggestion before anything is fetched; approved podcast feeds are handed to rssamplifier, everything else becomes a source here.

• search_profiles

  People: one entry per person assembled from every app that serves their OpenProfile.md (podcasters from p0dcasters, public profiles from OutreachGraph). Search by name, headline or anything in the document; newest change first. Each…

• find_profile_by_linkedin

  The public profile a LinkedIn profile or company URL belongs to (linkedin.com/in/… or /company/…), or null. LinkedIn only: profiles are never looked up by email.

• get_profile

  One person by id, `<slug>-<id>` or handle: the parsed view and the OpenProfile.md as served.

• claim_profile

  Claim a profile as the key owner (needs a key). Proven when the key owner’s email is one the profile lists, or when the person’s site or show page links back to the profile’s nichedb page. An admin may claim on behalf of an email.

• update_profile

  Edit a profile you own (needs a key). Send `markdown`, a whole OpenProfile.md that replaces what you wrote before, or any of `name`, `headline`, `emoji`, `pronouns`, `web`, `identity` (key: value, null removes), `sections` (name: body…

• add_source

  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.

• run_source

  Fetch a source now instead of waiting for its schedule (needs a key; owner or admin).

• search_tlds

  Top-level domains: every label in IANA's root, with type, registry, RDAP server and each registrar's one-year register/renew/transfer price (Porkbun, Dynadot, Cloudflare, OVHcloud). Sorted by renewal by default, because the first year is…

• get_tld

  One top-level domain: type, registry, RDAP server, when it entered or left the root, every registrar price (register, renew, transfer, restore, promotions, privacy, restrictions) and its change history.

• tld_changes

  Top-level domains added to or removed from IANA's root, newest first, with the IANA list version each happened in. Nobody else publishes this diff.

• check_domain

  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)…

• business_standing

  Is a business on anybody's list? Give its `name`, and any of `domain`, `state` (two letters), `number` (state entity number) and `ein`. Answers with `standing` (flagged, incomplete or clear; clear only when every list was checked and…

• reputation_lookup

  Is an IP address or a domain on a blocklist? Give `indicator` (an IPv4/IPv6 address or a domain; a URL is reduced to its host). Answers `listed`, a rough 0-100 `score` with the `reasons` behind it, the nichedb /traffic record (addresses…

• traffic_list

  The nichedb /traffic blocklist: IP addresses our own servers banned for exploit attempts, scanning, brute force or spam, each published only after a reviewer (a person, or riotcoder applying published rules) read the evidence and approved…