consulting.sequel/agent-tools
REMOTE · API.SEQUEL.CONSULTING
Sequel, leading Italian digital media consultancy: request a quote, site check, SEO/GEO insights.
Available components
Last scanned (22 hours ago)
Scores higher than 97% 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 717 tokens (~179/item across 4 items; 4 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 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 18 Oct 26 0
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 17 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
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://api.sequel.consulting/mcp.php
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sequel.consulting | CN=WE1,O=Google Trust Services,C=US | 30 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | c02a532d98270c220e46af10bc9ec504 |
| SANs: sequel.consulting, api.sequel.consulting, *.api.sequel.consulting | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.sequel.consulting. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| consulting. | DS published | 19711 | 8 | Verified |
| sequel.consulting. | DS published | 2371 | 13 | Verified |
| api.sequel.consulting. | 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=15768000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.sequel.consulting/mcp.php | Verified | 200 | |
| http (plaintext) | http://api.sequel.consulting/mcp.php | HTTPS enforced | 301 | https://api.sequel.consulting/mcp.php |
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 →
google_updates_status Stato update Google ~58
Riporta gli ultimi update di ranking confermati ufficialmente da Google e indica se ce n'è uno in rollout in questo momento. Dati dal monitor live di Sequel.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Lingua della risposta (default it) |
No output schema declared.
No examples provided.
quick_site_check Controllo agent-readiness rapido ~118
Esegue 4 controlli essenziali di prontezza per gli agenti AI su un sito (robots.txt, regole bot AI/Content-Signal, llms.txt, dati strutturati) e restituisce un mini-verdetto. È un assaggio: il report completo è sullo strumento agent-ready di Sequel.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Lingua del verdetto (default it) |
| url | string | yes | URL o dominio del sito da controllare (es. https://esempio.it) |
No output schema declared.
No examples provided.
request_quote Richiedi un preventivo a Sequel ~175
Invia una richiesta di preventivo a Sequel Consulting (sequel.consulting) per servizi di consulenza: SEO, GEO/AI visibility, assessment, adozione AI, contenuti, tecnologia. Il team risponde via email, di norma entro un giorno lavorativo.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Azienda (opzionale) |
| string | yes | Email a cui Sequel risponderà | |
| language | string | – | Lingua preferita per la risposta (default it) |
| name | string | yes | Nome e cognome del richiedente |
| need | string | yes | Descrizione della esigenza, es. "assessment SEO/GEO per un ecommerce" (10-2000 caratteri) |
| website | string | – | Sito web della azienda (opzionale) |
No output schema declared.
No examples provided.
search_insights Cerca negli approfondimenti Sequel ~117
Cerca tra gli articoli dell'Osservatorio Sequel e le pagine servizi/strumenti: SEO, GEO, visibilità sulle AI, Google update, AI Act, editoria e media digitale. Restituisce i 3 contenuti più pertinenti con link (anche in versione Markdown).
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Filtra per lingua (default: entrambe) |
| query | string | yes | Argomento o domanda (min 3 caratteri), es. "AI Act obblighi" o "Google core update" |
No output schema declared.
No examples provided.
How do I install the consulting.sequel/agent-tools MCP server?
consulting.sequel/agent-tools is a hosted endpoint at https://api.sequel.consulting/mcp.php, 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 · api.sequel.consulting
claude mcp add --transport http consulting-sequel-agent-tools 'https://api.sequel.consulting/mcp.php'
What is the consulting.sequel/agent-tools MCP server?
consulting.sequel/agent-tools is an MCP server listed in the public MCP registry as consulting.sequel/agent-tools. Sequel, leading Italian digital media consultancy: request a quote, site check, SEO/GEO insights. This page covers its hosted endpoint (https://api.sequel.consulting/mcp.php).
Is the consulting.sequel/agent-tools MCP server safe to use?
consulting.sequel/agent-tools scores 89 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 consulting.sequel/agent-tools MCP server expose?
consulting.sequel/agent-tools exposes 4 tools: request_quote, quick_site_check, search_insights, google_updates_status. Their descriptions and schemas cost roughly 468 tokens of context every time the server is loaded.
Does the consulting.sequel/agent-tools MCP server require authentication?
No. We connected to consulting.sequel/agent-tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the consulting.sequel/agent-tools MCP server still maintained?
consulting.sequel/agent-tools 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 consulting.sequel/agent-tools MCP server?
VerifyMCP ran 13 checks on consulting.sequel/agent-tools, 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.