AgentMart Site Check
Reads a website's public setup from the outside: HTTPS and security headers, certificate dates, SPF and DMARC, privacy, terms and contact pages, and files for AI agents. No sign-in.
- Brand
- AgentMart
- Category
- Developer Tools
- Primary Subcategory
- Application Security & Vulnerability Management
Integration details
Description
AgentMart Site Check reads the public setup of a website, the way any visitor or AI agent sees it from the outside. Give it a domain such as example.com. It checks HTTPS and security headers, certificate dates, email sender records (SPF and DMARC), whether privacy, terms and contact pages can be found, and files for AI agents (llms.txt, robots.txt and MCP). Each item comes back as pass, warn, fail or not checked, with plain steps to fix it. How it reads: at most 24 requests to the site per check, one of them over plain http to see whether the site moves visitors to HTTPS, plus public DNS questions. If the site names an MCP server, the check sends it the standard MCP opening messages, asks for its list of tools and ends the session. It follows the site's robots.txt rules for AgentMart-Check. It never logs in, fills in forms or changes anything. What it returns: our own fixed wording and numbers. No text from the checked site is copied into a result. A result is kept for 7 days and can be shown again by its check_id. A repeat for the same domain within 15 minutes gives the same result, unless you ask for a fresh check. Limits: a result describes that moment only. It is not a security audit, and it says nothing about the company's servers, code, staff or how it handles data. No account and no sign-in. Site owners can stop checks of their domain with a DNS TXT record agentmart-check=no on _agentmart-check.<their domain>, or by writing to us. Made by Ciphyr Tech OÜ (Estonia), the company that runs AgentMart.
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Primary Subcategory
- Application Security & Vulnerability Management
- Secondary Subcategories
- None listed
- Brand
- AgentMart
- Access
- No account required
- First tracked
- 2026-10-23
- Tool count
- 2
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competing in Claude Application Security & Vulnerability Management
View Category2 tools agents can invoke
AgentMart Site Check Claude Connector FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve AgentMart Site Check's Claude Connector discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are AgentMart Site Check alternatives on Claude?
As of 2026-10-26, AgentMart Site Check competes with CloudBees Unify MCP Server, ActiveLayer, Affirmed AI, AgentAvow, AI Website Security, Apiiro Guardian, Arcjet, Aribot and 28 more in Claude Application Security & Vulnerability Management, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.