agosint
REMOTE · AGOSINT.SHVEIK.DEV
Company and domain due diligence for agents: registers, sanctions, VAT, domain. Pay per call.
Available components
Last scanned (16 hours ago)
Scores higher than 68% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Security
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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 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 Usability78
- 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 2156 tokens (~154/item across 14 items; 10 tools + 4 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 16 Oct 26 0
- Tool “due-diligence” rewrote its description, which is the text the model reads security
- 15 Oct 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.
- 14 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Oct 26 74
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 16 Oct 2026 · Probed https://agosint.shveik.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agosint.shveik.dev | CN=YE1,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6a67d5a3a228aa96f1d94c7d2f495140fa9 |
| SANs: agosint.shveik.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agosint.shveik.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| shveik.dev. | 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=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agosint.shveik.dev/mcp | Verified | 200 | |
| http (plaintext) | http://agosint.shveik.dev/mcp | HTTPS enforced | 308 | https://agosint.shveik.dev/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 →
company Business registry lookup ~307
Business registry lookup: company identity and legal entity enrichment as structured JSON, by registration number, name and country, VAT number, LEI or website. Registers of Czechia, Norway, the United Kingdom, France, Finland, US SEC filers and every LEI holder. Use when: you need the official identity of one company.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | two-letter ISO country code; required with id or name; CZ, NO, GB and US have their own official register, any other country is looked up in GLEIF |
| domain | string | – | a company website as a bare domain: the legal entity is identified from the site's legal notice, certificate and public records and its register record returned; not charged when the site cannot be t… |
| id | string | – | the register id: CZ ICO, NO organisation number, GB company number, US ticker or CIK, or a registration number for other countries |
| lei | string | – | a 20-character legal entity identifier (any country; no country needed); when the entity's own register is one we read, that record is returned with the LEI and its parents |
| name | string | – | a company name; several matches return a short candidate list with ids |
| vat | string | – | a VAT number of a country whose number contains the register id (CZ, FR, FI, NO); no country needed. Send exactly one of id, name, lei, vat or domain |
No output schema declared.
No examples provided.
company-de German commercial register record ~211
German commercial register (Handelsregister) record: register court and number, legal form, status, seat, capital, representation rules, officers and history. Slower (about a minute). Use when: the company is German. Not offered on Solana: pay on Base or Polygon.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | seat city |
| include_deleted | boolean | – | also return companies deleted from the register |
| legal_form | string | – | legal form, e.g. GmbH or AG |
| limit | integer | – | most company records to return and pay for (1 to 5, default 1) |
| match | string | – | how the words of the name combine |
| name | string | yes | company name words as in the register |
| postal_code | string | – | seat postal code |
| register_court | string | – | the register court, e.g. München |
| register_number | string | – | exact register number |
| register_type | string | – | restrict to one register |
No output schema declared.
No examples provided.
domain Domain intelligence and phishing-risk signals ~130
Domain intelligence and phishing-risk signals: domain age and expiry (RDAP/WHOIS), registrar, DNS (A, AAAA, MX, NS, TXT, CAA), SPF, DMARC and MTA-STS, DNSSEC, TLS certificate issuer and expiry, hosting network, and the company behind the site when it can be identified. Use when: deciding whether a domain, link or email sender is legitimate, or checking a domain's mail setup.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | a public domain name such as example.com (an internationalised name is accepted); no URL, port or IP address |
No output schema declared.
No examples provided.
due-diligence Company due diligence in one call ~328
Company due diligence in one call (KYB, vendor and supplier checks). Give a company name and country, a registry number, an EU VAT number, an LEI or a website domain. Returns the legal entity from the official register, LEI and parents, VAT validity, a sanctions screen (OFAC, EU, UK) of the company and officers, and the domain's age, mail and TLS, as signed pass/warn/fail checks with sources. Use when you must decide whether to trust an unknown company.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | two-letter ISO country code; required with name or id; not used with lei, vat or domain |
| domain | string | – | the company's website as a bare domain such as example.com; the legal entity is identified from the site's own legal notice, its certificate and public records, and the call is not charged when it ca… |
| id | string | – | a register number of the country (CZ ICO, NO organisation number, GB company number, FR SIREN or SIRET, FI business id, DE register number such as HRB 12345, US CIK or ticker); use with country |
| include | array | – | the sections wanted; default all five |
| lei | string | – | a 20-character legal entity identifier |
| name | string | – | a company name; use with country. Send exactly one of name, id, lei, vat or domain |
| vat | string | – | an EU or Norwegian VAT number with its country prefix, such as CZ45274649 |
No output schema declared.
No examples provided.
feedback Send feedback ~117
Free. Tell the people who run this service what worked, what failed or what you miss: a bug, an idea or a thanks. A person reads it. No payment, no account; limited to a few messages an hour.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | optional: how we can reach you or your operator |
| kind | string | – | – |
| message | string | yes | what worked, what did not, what you miss; no secrets or private data |
| route | string | – | the route the feedback is about, if any |
No output schema declared.
No examples provided.
network Holder of an AS number or IP address ~82
IP address or AS number lookup: holder, announced prefixes, origin AS, country, RPKI status and abuse contact. Use when: you need to know who runs an IP address or network.
| Name | Type | Req | Description |
|---|---|---|---|
| asn | string | – | an AS number such as AS3333 or 3333 |
| ip | string | – | a public IPv4 or IPv6 address |
No output schema declared.
No examples provided.
preview Free preview before you pay ~124
Free check before you pay: whether a request can be answered and what it would return. Up to three matching companies (name, number, country, status), whether a VAT number's format and check digit are valid, whether a domain resolves and has mail servers, and the price. Use when: you are not sure the paid call will find the right subject.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | the body you would send to that route |
| route | string | yes | the route to preview: due-diligence, company, company-de, domain, network, sanctions, vat |
No output schema declared.
No examples provided.
sanctions Sanctions screening ~282
Sanctions screening against the official OFAC SDN, EU consolidated and UK lists with fuzzy name matching, a score per hit, the programme and each list's publication date. Screen a company or person name (optionally with country or birth date) or a crypto wallet address. Use when: screening a counterparty, supplier, customer or wallet before a payment or onboarding. A screening aid, not a compliance determination.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_date | string | – | a person's birth date, YYYY or YYYY-MM-DD; reported as corroboration of each hit |
| country | string | – | the subject's country (ISO code or English name); reported as corroboration of each hit, it does not change the score |
| kind | string | – | restrict matches to organisations (and vessels, aircraft) or to persons |
| lists | array | – | the lists to screen (default: all four) |
| name | string | – | the company or person name to screen; send either name or wallet |
| threshold | number | – | the lowest match score reported; 1.00 is an exact name or alias, 0.98 the same words in another order, lower scores are fuzzy matches |
| wallet | string | – | a crypto wallet address; an exact match against the digital-currency addresses listed on the OFAC SDN list (EVM addresses are case-insensitive) |
No output schema declared.
No examples provided.
vat EU VAT number validation ~186
EU VAT number validation against the official VIES service: valid or invalid, registered name and address, an optional check of the name you expect and, if you give your own VAT number, a VIES consultation number to keep as audit evidence. Norwegian numbers are checked against the Norwegian VAT register. Use when: onboarding an EU supplier or customer, or before paying an invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| expect_name | string | – | the company name you expect; the answer says whether it matches the registered name (match, partial, mismatch or not_checked) |
| requester_vat | string | – | your own EU VAT number: VIES then issues a consultation number, proof of the check to keep as audit evidence (not for Norwegian numbers) |
| vat | string | yes | the VAT number to check, with its country prefix (an EU member state, or NO for Norway), e.g. CZ45274649 |
No output schema declared.
No examples provided.
verify Verify an agosint answer ~37
Free: verify the signature and content hash of an agosint answer.
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | one record exactly as delivered, receipt included |
No output schema declared.
No examples provided.
How do I install the agosint MCP server?
agosint is a hosted endpoint at https://agosint.shveik.dev/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 · agosint.shveik.dev
claude mcp add --transport http dev-shveik-agosint 'https://agosint.shveik.dev/mcp'
What is the agosint MCP server?
agosint is an MCP server listed in the public MCP registry as dev.shveik/agosint. Company and domain due diligence for agents: registers, sanctions, VAT, domain. Pay per call. This page covers its hosted endpoint (https://agosint.shveik.dev/mcp).
Is the agosint MCP server safe to use?
agosint scores 75 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 agosint MCP server expose?
agosint exposes 10 tools: due-diligence, company, company-de, domain, network, and 5 more. Their descriptions and schemas cost roughly 1,804 tokens of context every time the server is loaded.
Does the agosint MCP server require authentication?
No. We connected to agosint without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the agosint MCP server still maintained?
agosint is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.