Proximens Oracle
REMOTE · WWW.PROXIMENS.NL
1000+ Generative Engine Optimization (GEO) principles exposed via MCP for AI agents.
Available components
Last scanned (8 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1536 tokens (~192/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Tool “proximens_geo_get_principle” rewrote its description, which is the text the model reads security
- Tool “proximens_geo_search_principles” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Tool “proximens_geo_search_principles” rewrote its description, which is the text the model reads security
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://www.proximens.nl/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.proximens.nl | CN=YR2,O=Let's Encrypt,C=US | 8 Sept 2026 | 7 Dec 2026 | RSA 2048 | SHA256-RSA | 63590512857c2749833d1b687cda56dd111 |
| SANs: www.proximens.nl | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.proximens.nl. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| nl. | DS published | 17153 | 13 | Verified |
| proximens.nl. | DS published | 55585 | 13 | Verified |
| www.proximens.nl. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://fonts.googleapis.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: https:; connect-src 'self' https://*.supabase.co wss://*.supabase.co; frame-src https://www.google.com; object-src 'none'; base-uri 'self'; frame-ancestors 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=self, microphone=self, geolocation=self |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.proximens.nl/mcp | Verified | 200 | |
| http (plaintext) | http://www.proximens.nl/mcp | HTTPS enforced | 308 | https://www.proximens.nl/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
proximens_geo_audit_url Audit URL against Proximens GEO Engine ~384
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.
| Name | Type | Req | Description |
|---|---|---|---|
| branche_hint | string | – | Branche hint in "main:sub" format, e.g. "health_wellness:yoga_studio". If omitted, principles are matched without branche filter. |
| client_name | string | – | Optional client identifier for the audit report header |
| max_issues | integer | – | Maximum issues to return (default 10) |
| mode | string | – | fast = quick signal checks (seconds); deep = full AI-synthesized consultancy report with sector benchmark (~30-50s) |
| url | string | yes | Target URL to audit |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| _wm | string | – | – |
| audit_id | string | yes | – |
| deep_mode | string | – | Deep-mode outcome: ok = full synthesized report; timeout_fallback = synthesis exceeded budget, fast result returned |
| error | string | – | – |
| matched_principles | array | – | – |
| recommendations | array | – | – |
| report_markdown | string | – | – |
| score | number | – | – |
| score_set | object | – | 7-dimension GEO scorecard (deep mode only) |
| sector | object | – | Detected sector benchmark cohort (deep mode only) |
| signals | object | – | – |
| status | string | yes | – |
| url | string | yes | – |
No examples provided.
proximens_geo_bulk_search Bulk Search Proximens GEO Engine ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| queries | array | yes | – |
| top_k_per_query | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| results | array | yes | – |
| total_matches | number | yes | – |
| total_queries | number | yes | – |
No examples provided.
proximens_geo_compare_urls Compare URLs against Proximens GEO Engine ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| competitor_url | string | yes | Competitor URL to compare against |
| self_url | string | yes | Your URL to audit |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| competitor_matched | array | yes | – |
| competitor_score | number | yes | – |
| competitor_url | string | yes | – |
| delta_principles | object | yes | – |
| error | string | – | – |
| insights | array | yes | – |
| self_matched | array | yes | – |
| self_score | number | yes | – |
| self_url | string | yes | – |
No examples provided.
proximens_geo_get_principle Get GEO principle by ID ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Principle UUID (from search_principles results) |
| Name | Type | Req | Description |
|---|---|---|---|
| _wm | string | – | – |
| branches | array | – | – |
| category | string | yes | – |
| confidence | number | yes | – |
| evidence_count | integer | – | – |
| full_text | string | – | – |
| id | string | yes | – |
| last_validated_at | string|null | – | – |
| similarity | number|null | – | – |
| source_diversity | integer | – | – |
| source_type | string|null | – | – |
| source_url | – | – | – |
| summary | string | yes | – |
| title | string | yes | – |
| upgrade_hint | string | – | – |
No examples provided.
proximens_geo_get_stats Get GEO Engine statistics ~88
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| confidence_distribution | object | – | – |
| fetched_at | string | – | – |
| last_distillation_at | string|null | – | – |
| last_validated_at | string|null | – | – |
| tier_hint | string | – | – |
| total_categories | integer | yes | – |
| total_evaluated | integer | – | – |
| total_principles | integer | yes | – |
No examples provided.
proximens_geo_list_categories List GEO principle categories ~133
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| cached | boolean | yes | – |
| categories | array | yes | – |
| total | integer | yes | – |
No examples provided.
proximens_geo_search_principles Search GEO principles (Proximens GEO Engine) ~305
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category (one of 13 GEO categories) |
| min_confidence | number | – | Minimum confidence score (0-1). Default 0.5 filters noise; raise to 0.8+ for high-confidence claims only |
| query | string | yes | Natural-language search query (e.g. "schema markup for local businesses" or "how to optimize for ChatGPT citations") |
| top_k | integer | – | Number of principles to return (max 25) |
| Name | Type | Req | Description |
|---|---|---|---|
| query_used | string | yes | – |
| results | array | yes | – |
| tier_note | string | – | Free-tier hint when top_k was capped |
| total_in_database | integer | yes | – |
No examples provided.
proximens_geo_synthesize_brief Synthesize Content Brief from Proximens GEO Engine ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| competitor_urls | array | – | – |
| target_branche | string | – | – |
| topic | string | yes | – |
| word_count_target | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | – | – |
| brief_id | string | yes | – |
| estimated_word_count | number | yes | – |
| faq_suggestions | array | – | – |
| principles_to_address | array | yes | – |
| schema_markup | array | – | – |
| suggested_structure | object | yes | – |
| topic | string | yes | – |
No examples provided.
How do I install the Proximens Oracle MCP server?
Proximens Oracle is a hosted endpoint at https://www.proximens.nl/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.proximens.nl
claude mcp add --transport http cryptosun-proximens-oracle 'https://www.proximens.nl/mcp'
What is the Proximens Oracle MCP server?
Proximens Oracle is an MCP server listed in the public MCP registry as io.github.cryptosun/proximens-oracle. 1000+ Generative Engine Optimization (GEO) principles exposed via MCP for AI agents. This page covers its hosted endpoint (https://www.proximens.nl/mcp).
Is the Proximens Oracle MCP server safe to use?
Proximens Oracle scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Proximens Oracle MCP server expose?
Proximens Oracle exposes 8 tools: proximens_geo_search_principles, proximens_geo_get_principle, proximens_geo_list_categories, proximens_geo_get_stats, proximens_geo_audit_url, and 3 more. Their descriptions and schemas cost roughly 1,536 tokens of context every time the server is loaded.
Does the Proximens Oracle MCP server require authentication?
No. We connected to Proximens Oracle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Proximens Oracle MCP server still maintained?
Proximens Oracle is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Proximens Oracle MCP server?
VerifyMCP ran 13 checks on Proximens Oracle, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.