io.github.AmauryDvl/serpmantics
REMOTE · APP.SERPMANTICS.COM · SCANNED AUG 3
French-first SEO: semantic content guides, scoring, E-E-A-T audits for Google, ChatGPT & Claude.
Available components
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 28 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3011 tokens (~107/item across 28 items; 28 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · app.serpmantics.com
claude mcp add --transport http amaurydvl-serpmantics https://app.serpmantics.com/api/mcp
[mcp_servers.amaurydvl-serpmantics] url = "https://app.serpmantics.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"amaurydvl-serpmantics": {
"type": "remote",
"url": "https://app.serpmantics.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add amaurydvl-serpmantics --url https://app.serpmantics.com/api/mcp --transport streamable-http
mcp_servers:
amaurydvl-serpmantics:
url: "https://app.serpmantics.com/api/mcp" {
"mcpServers": {
"amaurydvl-serpmantics": {
"type": "http",
"url": "https://app.serpmantics.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 63
First indexed and scored.
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 3 Aug 2026 · Probed https://app.serpmantics.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=serpmantics.com | CN=WE1,O=Google Trust Services,C=US | 20 Jul 2026 | 18 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | ab045b760d72f085134e46b31bb6b056 |
| SANs: serpmantics.com, *.serpmantics.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of app.serpmantics.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| serpmantics.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.serpmantics.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://app.serpmantics.com/api/mcp | HTTPS enforced | 301 | https://app.serpmantics.com/api/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.
create_eeat ~146
Start an E-E-A-T analysis on a guide content Starts an asynchronous E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) analysis on the HTML content provided for a given guide. The analysis runs in the background — use GET /api/v1/eeat to poll for results until `status` is `done` (or `failed`). **Note:** This endpoint uses tokens (check /api/v1/tokens-usage for the cost, might vary).
| Name | Type | Req | Description |
|---|---|---|---|
| guideId | string | yes | ID of the guide to analyze |
| html_content | string | yes | HTML of the article to analyze (without `<mark>` tags) |
No output schema declared.
No examples provided.
create_eeat_competitors ~196
Start an E-E-A-T analysis on a guide's top SERP competitors Starts an asynchronous E-E-A-T analysis on the top competitors of the guide's SERP. Each competitor is fetched and scored individually. Use GET /api/v1/eeat-competitors to poll for results until `pending` reaches `0`. **Token cost:** This endpoint charges `eeatCompetitorsTokensCostPerCompetitor` (see /api/v1/tokens-usage) per competitor analyzed, up to 10 competitors. Example: 10 competitors × 5 tokens = 50 tokens. 6 competitors × 5 tokens = 30 tokens. The number of competitors corresponds to the deduplicated URLs in the guide's top-10 SERP results (available via GET /api/v1/guide).
| Name | Type | Req | Description |
|---|---|---|---|
| guideId | string | yes | ID of the guide whose competitors should be analyzed |
No output schema declared.
No examples provided.
create_guides ~790
Create new guides Create one or more new guides based on provided queries. Each guide targets exactly ONE engine and ONE analysis mode, chosen with the optional `source` field (default `google`). How to request each guide type: 1. Google SERP guide (1 credit per guide): omit `source`, or pass `source: "google"`. Example payload: {"queries": ["best crm"], "lang": "en-us"} 1bis. Google AI Overview guide (1 credit per guide). Two modes, like AI engines: `source: "google_ai_overview"` builds the guide from the TEXT of Google's AI answers (AI Overview, completed with AI Mode answers) ; `source: "google_ai_overview_citations"` builds it from the content of the web SOURCES those answers cite (recommended for GEO). Same language/country parameters as a Google SERP guide, 1 credit per guide in both modes. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "google_ai_overview_citations"} 2. LLM ANSWER guide (4 credits per guide): pass the engine name alone, e.g. `source: "chatgpt"`. The guide is built from the answer text the AI generates for the query. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt"} 3. LLM CITATIONS guide (4 credits per guide) [RECOMMENDED AI mode]: pass the engine name with the `_citations` suffix, e.g. `source: "chatgpt_citations"`. The guide is built from the content of the web pages the AI cites in its answer. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt_citations"} Which AI mode to pick? For GEO (getting a page visible in AI answers), prefer `<engine>_citations`: AI engines send traffic by CITING pages as sources, so the winning move is to look like the pages they cite. The answer-text mode (`<engine>` alone) is mostly useful to analyze how the AI phrases its own answer. When in doubt, pick `<engine>_citations`. The same two modes exist for every AI engine (chatgpt, perplexity, claude, gemini, grok, mistral, deepseek). To optimize the…
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | yes | Language code for the guides |
| queries | array | yes | Array of queries to create guides for |
| source | string | — | Target engine AND analysis mode the guide optimizes for. One guide = one source. `google` analyzes the Google SERP (1 credit per guide). Google's AI answers have the same two modes as AI engines : `g… |
No output schema declared.
No examples provided.
create_intent ~91
Generate search intent analysis for a guide Analyzes search intent for a guide and optionally analyzes provided content against that intent. **Note:** This endpoint uses tokens (check /api/v1/tokens-usage for the cost, might vary).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | — | Optional content to analyze against the intent (only after intent analysis was created) |
| guideId | string | yes | ID of the guide |
No output schema declared.
No examples provided.
create_internal_links ~68
Generate internal linking suggestions for a guide Analyzes a guide and generates internal linking suggestions based on content analysis. **Note:** This endpoint uses tokens (check /api/v1/tokens-usage for the cost, might vary).
| Name | Type | Req | Description |
|---|---|---|---|
| guideId | string | yes | ID of the guide |
No output schema declared.
No examples provided.
create_meta ~67
Generate SEO meta titles and descriptions for a guide Generates optimized meta titles and descriptions based on guide content analysis. **Note:** This endpoint uses tokens (check /api/v1/tokens-usage for the cost, might vary).
| Name | Type | Req | Description |
|---|---|---|---|
| guideId | string | yes | ID of the guide |
No output schema declared.
No examples provided.
create_outline ~65
Generate content outline for a guide Generates a content outline based on SERP analysis for a guide. **Note:** This endpoint uses tokens (check /api/v1/tokens-usage for the cost, might vary).
| Name | Type | Req | Description |
|---|---|---|---|
| guideId | string | yes | ID of the guide |
No output schema declared.
No examples provided.
create_score ~77
Analyze content optimization score Analyzes the optimization score of the provided content for a specific guide
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Content to analyze |
| guideId | string | yes | ID of the guide to analyze |
| saveToGuide | boolean | — | Whether to save the content and the analysis score back to the guide (default: true) |
No output schema declared.
No examples provided.
delete_guide ~32
Delete a guide Deletes a specific guide
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The ID of the guide to delete |
No output schema declared.
No examples provided.
delete_guides ~19
Delete multiple guides Deletes multiple guides at once
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delete_intent ~40
Delete generated intent analysis for a guide Removes previously generated intent analysis for the given guide.
| Name | Type | Req | Description |
|---|---|---|---|
| guideId | string | yes | ID of the guide |
No output schema declared.
No examples provided.
delete_internal_links ~42
Delete generated internal-links suggestions for a guide Removes previously generated internal-links suggestions for the given guide.
| Name | Type | Req | Description |
|---|---|---|---|
| guideId | string | yes | ID of the guide |
No output schema declared.
No examples provided.
delete_meta ~40
Delete generated meta for a guide Removes previously generated meta titles/descriptions for the given guide.
| Name | Type | Req | Description |
|---|---|---|---|
| guideId | string | yes | ID of the guide |
No output schema declared.
No examples provided.
delete_outline ~38
Delete generated outline for a guide Removes previously generated outline data for the given guide.
| Name | Type | Req | Description |
|---|---|---|---|
| guideId | string | yes | ID of the guide |
No output schema declared.
No examples provided.
get_aissistant_tokens ~126
Get the current user's available AI tokens Returns the number of AI tokens available to the authenticated user. These tokens fund EVERY AI feature in SERPmantics — meta, outline, intent, internal-links, EEAT, EEAT competitors, score, AND the AISSistant prompts. The endpoint lives under /aissistant for historical reasons but the balance is shared across all AI features. Do NOT confuse with guide-creation credits (see /api/v1/credits). For a combined view (credits + tokens) prefer /api/v1/credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_credit_ledger ~176
Grand-livre crédits d'un compte (admin) Timeline complète et immuable des mouvements de crédits d'un utilisateur (octrois, consommations, refunds, resets, ajustements admin), avec libellés FR en clair, delta signé, solde après, source, auteur et référence. Inclut le solde reconstruit à une date arbitraire (paramètre `at`) et un contrôle de cohérence (solde == dernier balanceAfter == somme des deltas). Réservé aux administrateurs. Lecture seule.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | — | Date ISO pour reconstruire le solde à cet instant (point-in-time). |
| limit | number | — | Nombre maximum de lignes (défaut 200, max 1000). |
| userId | string | yes | Identifiant Mongo de l'utilisateur. |
No output schema declared.
No examples provided.
get_credits ~176
Get user balance (guide credits + AI tokens) Returns the authenticated user's full balance. SERPmantics has TWO distinct currencies: - **credits** (`credits`): how many NEW GUIDES the user can still create. Consumed once per guide creation. `"unlimited"` if the user's plan grants unlimited guide creation (`hasUnlimitedCredits: true`). - **AI tokens** (`tokens`): pool consumed by every AI feature (meta, outline, intent, internal-links, EEAT, EEAT competitors, score…). Each feature has its own cost — call `/api/v1/tokens-usage` to get the per-feature pricing. Do not confuse the two: running out of `credits` blocks new guides; running out of `tokens` blocks AI features inside existing guides.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_eeat ~162
Get E-E-A-T analysis results Retrieves the result of an E-E-A-T analysis. Either pass `eeatId` (returned by POST /api/v1/eeat) to fetch a specific analysis, or pass `guideId` to fetch the latest analysis for that guide. Poll this endpoint until `status` is `done` (results available) or `failed`.
| Name | Type | Req | Description |
|---|---|---|---|
| eeatId | string | — | ID of a specific analysis (returned by POST /api/v1/eeat). Either `eeatId` or `guideId` must be provided. |
| guideId | string | — | ID of the guide whose latest analysis should be returned. Either `eeatId` or `guideId` must be provided. |
No output schema declared.
No examples provided.
get_eeat_competitors ~96
Get E-E-A-T analysis results for a guide's competitors Retrieves the E-E-A-T analysis results for the top competitors of a guide. Poll this endpoint until `pending` is `0` to know when the full analysis is complete. Individual competitor results are available as soon as their `status` is `done`.
| Name | Type | Req | Description |
|---|---|---|---|
| guideId | string | yes | ID of the guide whose competitors should be returned |
No output schema declared.
No examples provided.
get_guide ~38
Get data for a specific guide Retrieves details of a specific guide
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The ID of the guide to retrieve |
No output schema declared.
No examples provided.
get_guides ~43
List user's guides Returns a list of guides for the authenticated user
| Name | Type | Req | Description |
|---|---|---|---|
| page | — | — | Page number for pagination |
| pageSize | — | — | Number of guides per page |
No output schema declared.
No examples provided.
get_intent ~39
Get search intent analysis for a guide Retrieves existing intent analysis results for a guide
| Name | Type | Req | Description |
|---|---|---|---|
| guideId | string | yes | ID of the guide |
No output schema declared.
No examples provided.
get_internal_links ~39
Get internal linking suggestions for a guide Retrieves existing internal linking suggestions for a guide
| Name | Type | Req | Description |
|---|---|---|---|
| guideId | string | yes | ID of the guide |
No output schema declared.
No examples provided.
get_meta ~42
Get generated meta titles and descriptions for a guide Retrieves generated SEO meta titles and descriptions for a guide
| Name | Type | Req | Description |
|---|---|---|---|
| guideId | string | yes | ID of the guide |
No output schema declared.
No examples provided.
get_outline ~43
Get generated page structure for a guide Retrieves the generated page structure (flat heading list) for a guide.
| Name | Type | Req | Description |
|---|---|---|---|
| guideId | string | yes | ID of the guide |
No output schema declared.
No examples provided.
get_tokens_usage ~99
Get API token usage costs for different endpoints Returns the number of tokens required for each API endpoint operation. Note: `eeatCompetitorsTokensCostPerCompetitor` is a **per-competitor** cost. The total cost of POST /api/v1/eeat-competitors equals this value × the number of competitors analyzed (deduplicated URLs in the guide's top-10 SERP, capped at 10).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_usage ~49
Get current API usage and quota status Returns the current period's API guide usage, quota limit, remaining count and the renewal date. Aligned on the Stripe subscription billing cycle. Does not consume credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
update_guide ~172
Update a guide Updates editable fields of a specific guide (group, status, share state, linked URL, meta, hidden expressions). Only owners may update.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | — | Group/folder the guide belongs to (triggers cannibalisation analysis on previous and new group) |
| hiddenExpressions | array | — | Expressions to hide from the optimisation suggestions |
| id | string | yes | The ID of the guide to update |
| linkedUrl | string | — | Public URL where the guide content is published (validated as URL) |
| meta | object | — | SEO meta override for the guide |
| shareState | string | — | Sharing mode. Plan must allow shared-read or shared-edit, otherwise 403 is returned. |
| status | string | — | Editorial status of the guide. Empty string clears the status. |
No output schema declared.
No examples provided.