mcpbeat Sign in

Agentic Endpoints MCP Server

by oliverkiss Your server? Claim it
answering

Agentic Endpoints is answering right now. Last checked 12 min ago. It exposes 18 tools. Last commit 10 Sep 2026.

Pay-per-call tools for autonomous agents, settled in USDC on Base via x402.

Uptime history 6 days of history
6 days agonow
100.0%
Uptime 24h
92 of 92 checks
18
Tools
read from the server
162 ms
Response time
average over 24h
0
Stars
last commit 10 Sep 2026

What changed 10

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 5 September 2026. No other catalogue keeps this.

10 Sep 2 tools appeared meetings_summarize, x402_verify
10 Sep 2 tool descriptions were rewritten meetings_import, x402_verify
10 Sep a tool changed the parameters it asks for meetings_import
5 Sep 4 tools appeared meetings_get, meetings_import, meetings_list and 1 more
5 Sep a tool changed the parameters it asks for meetings_import

Nothing serious here today

Today is the operative word: we check Agentic Endpoints every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add agentic-endpoints --transport http https://ai.oliverkiss.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agentic-endpoints": {
      "url": "https://ai.oliverkiss.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.agentic-endpoints]
url = "https://ai.oliverkiss.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agentic-endpoints": {
      "url": "https://ai.oliverkiss.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "agentic-endpoints": {
      "url": "https://ai.oliverkiss.com/mcp"
    }
  }
}

Available tools 18

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

vault
vault_delete
Permanently delete an item. Requires the namespace_token. Costs $0.005 in USDC on Base, paid via the x402 protocol.
vault_exists
Check for a key without returning its ciphertext. Requires the namespace_token. Costs $0.001 in USDC on Base, paid via the x402 protocol.
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 have stored secrets and need to know what is there. Costs $0.001 in USDC on Base, paid via the x402 protocol.
vault_retrieve
Retrieve a previously stored ciphertext. Requires the namespace_token. Costs $0.02 in USDC on Base, paid via the x402 protocol.
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 and delete access to every secret in the namespace. There is no recovery if you lose the token. This tool is free; no payment is required.
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 namespace_token shown only once — store it immediately, because it is required by every later call and cannot be recovered. Pass if_match with an item's updated_at for a compare-and-swap write, or if_absent to create only; either returns status 'precondition_failed' rather than silently clobbering a concurrent write. Costs $0.02 in USDC on Base, paid via the x402 protocol.
meetings
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 text could not be found -- that is a broken record, not an empty meeting, so do not report it as one. Costs $0.002 in USDC on Base, paid via the x402 protocol.
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 so phrases still match. `visibility` is a required decision and cannot be guessed for you: 'queryable' stores plaintext, indexes it, and means this service can read it; 'private' stores ciphertext you encrypted yourself, which is unreadable here and therefore NEVER searchable. Send `transcript` for queryable and `ciphertext` for private -- the mismatched combinations are refused rather than silently doing the wrong thing. The first import into a namespace returns a namespace_token shown exactly once; save it or the namespace is unrecoverable. Costs $0.004 in USDC on Base, paid via the x402 protocol.
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 invisible to meetings_search. Costs $0.001 in USDC on Base, paid via the x402 protocol.
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 -- 'what did we decide about pricing', 'who owned the migration', 'when did we say we would ship'. Returns 'searched_meetings' and 'private_meetings_skipped': meetings imported as private are encrypted and CANNOT be searched, so if searched_meetings is 0 an empty result means nothing was searched, NOT that the topic was never discussed. Use meetings_get to read a full transcript once you have found the right meeting. Costs $0.006 in USDC on Base, paid via the x402 protocol.
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 pricing?', 'who owned the migration?') rather than a list of excerpts to read themselves. Pass the question as the user asked it -- this is NOT FTS5 syntax, and the terms actually searched come back as `terms` so you can check the retrieval. IMPORTANT: a 'no_matches' status means no answer was generated, and 'searched_meetings': 0 means every meeting is private and NOTHING was read -- neither is evidence the topic was never discussed, and you must not report it as such. Meetings imported as private are encrypted and can never contribute to an answer; `private_meetings_skipped` says how many were left out. A 'truncated' meeting in `consulted` had only part of its transcript read, so its silence on a point is not evidence either. Costs $0.030 in USDC on Base, paid via the x402 protocol.
once
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 posting an order. Returns one of: 'claimed' — you won, do the work, then call once_key_complete; 'in_progress' — another agent holds a live lease, wait retry_after seconds and do NOT do the work; 'duplicate' — already done, and the 'result' field carries the original outcome, so use it instead of repeating the work; 'held' — another agent claimed this key, set no lease, and has NOT completed it: there is no result and there may never be one, so do NOT do the work and do NOT treat it as done, because the key stays locked until expires_at; 'conflict' — the same key was claimed with a different payload hash, so your key derivation is wrong. Backed by a strongly consistent Durable Object; this is not something an agent can safely reimplement locally. Costs $0.001 in USDC on Base, paid via the x402 protocol.
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 effect. Always call this after the work succeeds — a claim with no recorded result leaves every other agent unable to learn what happened. Completion is final and cannot be overwritten. This tool is free; no payment is required.
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 result and allow the side effect to run twice. This tool is free; no payment is required.
compress
compress
Reduce text to fit a token budget, preserving whole sentences and reporting before/after token estimates. Costs $0.005 in USDC on Base, paid via the x402 protocol.
pdf
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.01 in USDC on Base, paid via the x402 protocol.
scrape
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.005 in USDC on Base, paid via the x402 protocol.
x402
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 single agent cannot see on its own -- above all, whether the address receiving the money has changed. A 'critical' entry in `drift` means something determining where funds go (pay_to, network or asset) is different from before: stop and confirm out of band. Read the LIVE `charges` in preference to any directory listing, and pass what the listing claimed as `expect` to have the disagreement reported. IMPORTANT: 'status':'ok' is NOT an endorsement -- it only means a challenge was read and recorded. It cannot tell you whether the operator will deliver anything for your money. 'first_observation':true means there is no history at all, so an empty `drift` proves nothing. ALWAYS read `prior_criticals`: `drift` only compares against the last observation, so an endpoint that swapped its payee earlier shows an empty `drift` once that swap became the baseline -- a non-zero `prior_criticals` means it has changed where money goes before, and that is true no matter how clean today's look is. 'status':'unreachable' is not evidence of fraud and not evidence of health; do not pay on it either way. A null `price_usd` means the token's units are unknown here and the amount was NOT converted -- do not assume it is small. Costs $0.003 in USDC on Base, paid via the x402 protocol.

Endpoints

URLTransportStateLatencyChecked
https://ai.oliverkiss.com/mcp streamable-http answering 228 ms 12 min ago

Alternatives to Agentic Endpoints

same job, measured the same way
Agentreader MCP
by ajanani1

11 pay-per-call web tools for AI agents, auto-paid in USDC on Base via x402. No API keys.

10 installs/wk local only
Yelp data for agents
by fetcher-yelp

4 Yelp endpoints. Pay per call in USDC via x402.

6 tools answering
TikTok data for agents
by fetcher-tiktok

13 TikTok endpoints. Pay per call in USDC via x402.

15 tools answering
App Store data for agents
by fetcher-appstore

9 App Store endpoints. Pay per call in USDC via x402.

11 tools answering
Twitter / X data for agents
by fetcher-twitter

15 Twitter / X endpoints. Pay per call in USDC via x402.

17 tools answering
Google Search data for agents
by fetcher-google

1 Google Search endpoints. Pay per call in USDC via x402.

3 tools answering
Reddit data for agents
by fetcher-reddit

15 Reddit endpoints. Pay per call in USDC via x402.

17 tools answering
Instagram data for agents
by fetcher-instagram

16 Instagram endpoints. Pay per call in USDC via x402.

18 tools answering

Agentic Endpoints — questions

Answers built from our own checks of this server.

What can Agentic Endpoints do?
It exposes 18 tools, read directly from the server on our last check. Among them: compress, meetings_get, meetings_import, meetings_list, meetings_search, meetings_summarize and 12 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Agentic Endpoints mostly used for?
Its tools cluster around vault, meetings and once. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Agentic Endpoints working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 162 ms. The bar chart above shows every period we have measured.
How do I connect Agentic Endpoints?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Agentic Endpoints need an API key?
No. Agentic Endpoints completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 18 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agentic Endpoints?
It answers our handshake in 162 ms on average, which is faster than 74% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Agentic Endpoints open source?
Yes — it is published under the MIT licence, written in TypeScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.