mcpbeat Sign in

Proximens Oracle MCP Server

by cryptosun Your server? Claim it
not responding

Proximens Oracle is listed as active in the registry but did not answer our last check. It exposes 8 tools.

1000+ Generative Engine Optimization (GEO) principles exposed via MCP for AI agents.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 90 days of history · worst day 75%
90 days agonow
98.9%
Uptime 24h
90 of 91 checks
8
Tools
read from the server
251 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 2

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

2 Nov 2 tool descriptions were rewritten proximens_geo_get_principle, proximens_geo_search_principles

Proximens Oracle does not always answer

Over the last week it answered 92.5% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

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 11 min ago.

run in your terminal
claude mcp add proximens-oracle --transport http https://www.proximens.nl/mcp
Settings → Connectors → Add custom connector, then paste this address
https://www.proximens.nl/mcp
~/.codex/config.toml
[mcp_servers.proximens-oracle]
url = "https://www.proximens.nl/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "proximens-oracle": {
      "url": "https://www.proximens.nl/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "proximens-oracle": {
      "type": "http",
      "url": "https://www.proximens.nl/mcp"
    }
  }
}

Available tools 8

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

proximens
proximens_geo_audit_url
Pro-tier. Fetch and analyze a web page, then audit it against the Proximens GEO Engine principles across all major GEO dimensions (structured data, crawler access, content depth, freshness, E-E-A-T, multimodal). INPUT: url (required, http/https); optional mode ("fast" = quick signal checks, returns in seconds — the default; "deep" = a full AI-synthesized consultancy report in Dutch with a 7-dimension scorecard and sector benchmark, takes ~30-50s), client_name (report header), branche_hint ("main:sub", e.g. "health_wellness:yoga_studio"), max_issues (1-25, default 10). RETURNS: JSON with a 0-100 score, severity-ranked issues (critical/major/minor) each with a finding and an actionable suggestion, top recommendations, and a markdown report; deep mode additionally returns score_set (7 GEO dimensions), sector (benchmark cohort), and a full consultancy-grade report_markdown (deep_mode="timeout_fallback" means the synthesis exceeded its budget and the fast result was returned instead). USE fast mode for quick checks and bulk triage; USE deep mode when you need a client-ready audit report. Free tier is blocked.
proximens_geo_bulk_search
Pro-tier. Run many GEO-principle searches in a single fast call. INPUT: queries (array of 2-100 natural-language strings, each 3-500 chars); optional top_k_per_query (1-10, default 5) and category filter. RETURNS: JSON with a results array (per query: the query, its matched principles, and a count), plus total_queries, total_matches and processing time. USE WHEN you need many lookups at once, e.g. a full-site audit or a keyword list, instead of repeated search_principles calls.
proximens_geo_compare_urls
Pro-tier. Fetch two web pages (your URL and a competitor's) and audit both against the Proximens GEO Engine principles using the same audit engine as audit_url, then compute the delta. INPUT: self_url and competitor_url (both required, http/https). RETURNS: JSON with a 0-100 score per URL (same scoring as audit_url), the principles each page satisfies, the principles each page VIOLATES that the other satisfies (delta_principles), and strategic insights on where to close the gap. USE WHEN you want a competitive GEO gap analysis between your page and a rival's.
proximens_geo_get_principle
Fetch one GEO principle from the Proximens GEO Engine by its UUID. INPUT: id (REQUIRED, UUID string taken from a prior search_principles result — call search_principles first if you do not have one). RETURNS: a single principle as JSON with id, title, summary, category and confidence; Pro/Enterprise tiers additionally return full_text, source_url, source_type, evidence_count and the last-validated timestamp. USE WHEN you already have a principle id and need its full detail — typically to drill down after search_principles.
proximens_geo_get_stats
Return live aggregate statistics for the Proximens GEO Engine knowledge base. INPUT: none. RETURNS: JSON with total_principles (high-confidence count), total_categories, and on Pro/Enterprise also extended quality metrics (full corpus size and a confidence_distribution) plus the last-validated timestamp. USE WHEN you need to gauge the size and quality of the corpus before relying on it.
proximens_geo_list_categories
List the GEO principle taxonomy of the Proximens GEO Engine with a live count of high-confidence principles per category. INPUT: none. RETURNS: JSON with a categories array of {category, count, description} sorted by count, plus a reconciled total that matches get_stats.total_principles. Categories: technical, structured-data, ai-search, content, e-e-a-t, freshness, multimodal, user-signals, performance, query-intent, internal-linking, mobile, other. USE WHEN you want to discover which categories exist before narrowing a search_principles call with the category filter.
proximens_geo_search_principles
Semantic search over the Proximens GEO Engine: a curated, continuously-updated knowledge base of 8.000+ Generative Engine Optimization (GEO/AEO) principles, each graded by a 0-1 confidence score and traceable to a source. INPUT: query (REQUIRED, natural language, 3-500 chars, e.g. "how does ChatGPT choose which FAQ to cite"); optional category (one of 13 GEO categories), top_k (1-25, default 10), min_confidence (0-1, default 0.5). RETURNS: ranked principles as JSON, each with id, title, summary, category, confidence and a relevance score; Pro/Enterprise tiers additionally return full_text and source. USE WHEN you need evidence-backed answers about how AI search engines (ChatGPT, Perplexity, Gemini, Google AI Overviews, Copilot) select, rank and cite web content.
proximens_geo_synthesize_brief
Generate a structured, GEO-optimized content brief for a topic using the Proximens GEO Engine. INPUT: topic (3-200 chars); optional target_branche (one of 7 verticals), word_count_target (300-5000, default 1500) and up to 3 competitor_urls. RETURNS: JSON with a suggested H1 and H2 section structure with key points, the principles the content should address, and (Pro/Enterprise) FAQ suggestions and recommended schema.org markup. USE WHEN you need to brief a writer so a page is built to be cited by AI search engines.

Endpoints

URLTransportStateLatencyChecked
https://www.proximens.nl/mcp streamable-http answering 86 ms 11 min ago

Alternatives to Proximens Oracle

same job, measured the same way
Execute crypto-price-oracle-mcp
by evozim

Premium agentic endpoint for crypto-price-oracle-mcp.

1 tools answering
Cryptopolitan MCP
by 4dmrkey

Real-time crypto news, analysis, and price predictions for AI agents via MCP.

5 tools answering
Agent Data Pro
by orionsmithers

Research articles and live crypto prices for AI agents via x402 on Base.

6 tools answering
Valta
by billionaire664

Financial governance for AI agents — spend gates and audit trail exposed as MCP tools.

34 installs/wk local only
Flyto Core
by flytohub

Execution engine for AI agents. 412 modules: browser, file, Docker, data, crypto.

2 530 installs/wk local only
Base Multi Wallet MCP
by lordbasilaiassistant-sudo

MCP server for AI agents to manage multiple wallets with coordinated trading and batch operations on

126 installs/wk local only
MarketTrace Crypto MCP
by markettrace

Crypto perps for AI agents: funding, OI, liquidations, order book, CVD, volume profile, footprint.

answering
Paddock
by paddock

Pre-payment verification for AI agents.

13 tools answering

Proximens Oracle — questions

Answers built from our own checks of this server.

What can Proximens Oracle do?
It exposes 8 tools, read directly from the server on our last check. Among them: proximens_geo_audit_url, proximens_geo_bulk_search, proximens_geo_compare_urls, proximens_geo_get_principle, proximens_geo_get_stats, proximens_geo_list_categories and 2 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 →
Is Proximens Oracle working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 251 ms. The bar chart above shows every period we have measured.
Is Proximens Oracle still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Proximens Oracle as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Proximens Oracle?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Proximens Oracle need an API key?
No. Proximens Oracle completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Proximens Oracle?
It answers our handshake in 251 ms on average, which is faster than 57% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.