Avenity AI Visibility
REMOTE · AVENITY-AGENTIC-AUDIT.ONRENDER.COM · SCANNED SEP 20
Hireable AI-visibility service: get a business named in AI answers. Free audit + x402 hire.
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 → Why this is hard to score →
Endpoint Security57
- 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 connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Avenity AI Visibility MCP server?
Avenity AI Visibility is a hosted endpoint at https://avenity-agentic-audit.onrender.com/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 · avenity-agentic-audit.onrender.com
claude mcp add --transport http dankaten-avenity-agentic-audit 'https://avenity-agentic-audit.onrender.com/mcp'
{
"mcpServers": {
"dankaten-avenity-agentic-audit": {
"url": "https://avenity-agentic-audit.onrender.com/mcp"
}
}
} {
"servers": {
"dankaten-avenity-agentic-audit": {
"type": "http",
"url": "https://avenity-agentic-audit.onrender.com/mcp"
}
}
} [mcp_servers.dankaten-avenity-agentic-audit] url = "https://avenity-agentic-audit.onrender.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dankaten-avenity-agentic-audit": {
"type": "remote",
"url": "https://avenity-agentic-audit.onrender.com/mcp",
"enabled": true
}
}
} openclaw mcp add dankaten-avenity-agentic-audit --url 'https://avenity-agentic-audit.onrender.com/mcp' --transport streamable-http
mcp_servers:
dankaten-avenity-agentic-audit:
url: "https://avenity-agentic-audit.onrender.com/mcp" {
"McpServers": {
"dankaten-avenity-agentic-audit": {
"Transport": "http",
"Url": "https://avenity-agentic-audit.onrender.com/mcp"
}
}
} assistant mcp add dankaten-avenity-agentic-audit -t streamable-http -u 'https://avenity-agentic-audit.onrender.com/mcp'
{
"mcpServers": {
"dankaten-avenity-agentic-audit": {
"type": "http",
"url": "https://avenity-agentic-audit.onrender.com/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.
- 19 Sept 26 −53
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 6 Sept 26 0
- Tool “purchase_engagement” rewrote its description, which is the text the model reads security
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 3.4.4 → 4.0.3 functional
- “purchase_engagement” reworded the description of “payment_proof” cosmetic
- Tool “audit_business_visibility” changed its title: Audit Business Visibility cosmetic
- Tool “purchase_engagement” changed its title: Purchase Engagement cosmetic
- Tool “request_engagement_quote” changed its title: Request Engagement Quote cosmetic
- 1 Sept 26 +53
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Destructive annotations: pass 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
- 22 Aug 26 23
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.87 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ 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
- The server no longer declares the “experimental” capability functional
- 3 Aug 26 0
- HSTS header: unverified → fail ▼ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. 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 20 Sept 2026 · Probed https://avenity-agentic-audit.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 24 Jul 2026 | 22 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 756bcb97dcf1455f0ebf70e5dbe07256 |
| SANs: onrender.com, *.onrender.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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of avenity-agentic-audit.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.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 | 503 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://avenity-agentic-audit.onrender.com/mcp | HTTP error | 503 | |
| http (plaintext) | http://avenity-agentic-audit.onrender.com/mcp | HTTPS enforced | 301 | https://avenity-agentic-audit.onrender.com/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 →
audit_business_visibility Audit Business Visibility ~114
FREE. Check whether a business is named in AI answers for a specific money category in a specific place. This is the top-of-funnel: agents run it to diagnose a client.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | yes | The business being audited (e.g. "Gracey's Commercial Cleaning"). |
| category | string | yes | The specific buyer category / product line (e.g. "commercial janitorial"). |
| location | string | yes | City/region the buyers are in (e.g. "Conroe, TX"). |
Structured output declared, but exposes no named fields.
No examples provided.
purchase_engagement Purchase Engagement ~174
Hire Avenity. x402-GATED: without valid payment_proof this returns HTTP-402-shaped payment requirements (pay to Avenity's wallet). With payment_proof, it is verified and settled against the x402 facilitator before the engagement is confirmed — an engagement is only ever marked "acquired" after the facilitator confirms the payment actually settled on-chain.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | yes | client being engaged. |
| categories | array | yes | the categories/product lines to get named for. |
| contact | – | – | optional human contact for onboarding. |
| payment_proof | – | – | the x402 payment payload/settlement token from the agent's wallet (the X-PAYMENT header value: base64-encoded JSON). |
| tier | string | – | pricing tier (see request_engagement_quote). |
Structured output declared, but exposes no named fields.
No examples provided.
request_engagement_quote Request Engagement Quote ~112
FREE. Return the scope and price to get a business NAMED in AI answers for the given categories. Each category is a separate entity / data-engineering unit of work. tier: one of 'local' ($1500/mo, 3 categories), 'regional' ($3000/mo), 'national' ($5000/mo), or 'paige' ($300/mo monitoring/local).
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | yes | – |
| categories | array | yes | – |
| tier | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Avenity AI Visibility MCP server?
Avenity AI Visibility is an MCP server listed in the public MCP registry as io.github.DanKaten/avenity-agentic-audit. Hireable AI-visibility service: get a business named in AI answers. Free audit + x402 hire. This page covers its hosted endpoint (https://avenity-agentic-audit.onrender.com/mcp).
Is the Avenity AI Visibility MCP server safe to use?
Avenity AI Visibility scores 23 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 Avenity AI Visibility MCP server expose?
Avenity AI Visibility exposes 3 tools: audit_business_visibility, request_engagement_quote, purchase_engagement. Their descriptions and schemas cost roughly 400 tokens of context every time the server is loaded.
Does the Avenity AI Visibility MCP server require authentication?
No. We connected to Avenity AI Visibility without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Avenity AI Visibility MCP server still maintained?
Avenity AI Visibility is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.