Servidor MCP de Agentic Endpoints

• Nombre en el registrocom.agentic-endpoints/agentic-endpointsverificado en el registro MCP

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

• Estadorespondecomprobado el 2026-10-15
• Herramientas24
• El servidor se llamaagentic-endpoints
• Versión del servidor1.0.0
• Versión del protocolo2025-06-18

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

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 3 de los 7 días necesarios para juzgar su fiabilidad.

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 MCPtras una semanala nota necesita 7 comprobaciones diarias: 3 hasta ahora
• Respondiómidiendo3 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta193 ms
• Espacio en el contexto del agente≈ 7149 tokenslas definiciones de todas sus herramientas (24), que el agente lleva en cada turno
• Definiciones de herramientasA · 99 de 100
• Resultados tipados24 de 24 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin tipo: en 1 de 24

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 (30%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%) y uso (15%). 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 →

• meetings_search

  Ask a question across every meeting you have imported as queryable, and get back ranked excerpts with the meeting they came from. This is the tool to use when the user refers to something that was said, agreed, or decided in a call…

• x402_verify

  Call this BEFORE authorising payment to any x402 endpoint you did not write yourself. It fetches the endpoint's live payment challenge and compares it against every observation previously made by every other caller, so you learn things a…

• meetings_summarize

  Ask a plain-language question and get a written answer grounded in the user's own meeting transcripts, with the meeting id cited after each claim. Prefer this over meetings_search when the user wants an ANSWER ('what did we decide about…

• meetings_import

  Store a transcript so it can be searched later. Accepts a raw WebVTT or SRT export straight from Zoom, Teams, Meet or a notetaker -- you do NOT need to strip timestamps or parse it first, and cues split across timing boundaries are merged…

• meetings_get

  Fetch a single meeting by meeting_id, including its full transcript when it was imported as queryable. Use this after meetings_search has identified the meeting you want. A 'content_missing' status means the record exists but its stored…

• meetings_list

  List the meetings in a namespace newest first, with titles, dates, participants and whether each one is searchable. Never returns transcripts. Useful for orienting before a search, and for finding meetings that are private and therefore…

• once_key_claim

  Atomic idempotency witness. Claims a {namespace, action_key} pair exactly once, so a fleet of agents cannot perform the same side effect twice. Call this BEFORE any non-idempotent action such as sending an email, charging a card, or…

• once_key_complete

  Free. Records the result of work you performed under a claim from once_key_claim. Every later claim of that action_key returns 'duplicate' along with this result, which is what lets another agent continue without repeating the side…

• once_key_release

  Free. Surrenders a claimed action_key so a retry can start immediately instead of waiting out the lease. Call this when the work you claimed fails. Refuses if the key was already completed, because releasing it would discard the recorded…

• vault_store

  Store client-side encrypted data. This service holds no key that could decrypt it and never sees plaintext; note that the item key, namespace, alg label and size ARE stored in the clear. The first store claims the namespace and returns a…

• vault_retrieve

  Retrieve a previously stored ciphertext. Requires the namespace_token. Costs $0.02 in USDC on Base, paid via the x402 protocol, or from a credit token — call credits_trial for free credit if you have neither.

• vault_exists

  Check for a key without returning its ciphertext. Requires the namespace_token. Costs $0.005 in USDC on Base, paid via the x402 protocol, or from a credit token — call credits_trial for free credit if you have neither.

• vault_delete

  Permanently delete an item. Requires the namespace_token. Costs $0.005 in USDC on Base, paid via the x402 protocol, or from a credit token — call credits_trial for free credit if you have neither.

• vault_list

  List the keys held in a namespace with their metadata: alg, size, timestamps. Never returns ciphertext — use vault_retrieve for that. Each item's updated_at is the version to pass back as if_match on a conditional store. Use this when you…

• vault_rotate_token

  Free. Mints a new namespace_token and immediately invalidates the current one, which you must present to authorize the rotation. Do this whenever the token may have been exposed — a leaked token is otherwise permanent, unrevocable read…

• pdf_parse

  Extract text from a PDF by URL. Handles compressed streams, PDF 1.5+ object streams and ToUnicode CMaps, and reports encrypted or image-only documents honestly instead of returning garbage. Costs $0.020 in USDC on Base, paid via the x402…

• scrape

  Fetch a URL and return readable text or markdown, optionally narrowed by CSS selector. Requests to private, loopback and link-local addresses are refused, and every redirect hop is re-validated. Costs $0.010 in USDC on Base, paid via the…

• reach

  Send one GET to a URL as each of nine common clients (curl, node, Python urllib, Python requests, libwww-perl, a Chrome browser, GPTBot, ClaudeBot, Googlebot) and report which are refused and why, such as a Cloudflare 1010 block on…

• reach_report

  Order a full reachability report for one site: up to 20 pages, each checked from nine common clients. Returns a report_id and report_url at once; the pages are scanned in the background, about ten seconds each. The finished report gives…

• reach_report_status

  Free. Returns a reachability report by its report_id: progress while it scans, then the prioritised findings with causes, fix steps and reproducing commands, the per-page evidence, and a comparison with the previous scan after a re-scan…

• reach_report_rescan

  Free, up to three times within 30 days of ordering. Re-runs every page of a finished report so you can confirm a fix worked; the report then shows what was fixed, what remains and anything new. This tool is free; no payment is required.

• compress

  Reduce text to fit a token budget, preserving whole sentences and reporting before/after token estimates. Costs $0.010 in USDC on Base, paid via the x402 protocol, or from a credit token — call credits_trial for free credit if you have…

• credits_trial

  Free, and the first tool to call if any other tool has told you payment is required. Returns a credit_token carrying $0.10 of credit — roughly ten calls at the standard price — with no wallet, no signature, no account and no email. Pass…

• credits_balance

  Free. Reports the remaining balance on a credit token so you can tell 'out of credit' apart from 'the call failed', which otherwise look identical from the outside. This tool is free; no payment is required.