Avenity AI Visibility
REMOTE · AVENITY-AGENTIC-AUDIT.ONRENDER.COM · SCANNED AUG 3
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 →
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 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. See how to fix → 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 478 tokens (~159/item across 3 items; 3 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 Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 · avenity-agentic-audit.onrender.com
claude mcp add --transport http dankaten-avenity-agentic-audit 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": {
"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.
- 3 Aug 26 +10
- 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
- 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.
- 1 Aug 26 +29
- HSTS header: fail → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
- 31 Jul 26 +9
- 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 −46
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 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 58
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://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 |
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 | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://avenity-agentic-audit.onrender.com/mcp | Verified | 200 | |
| 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.
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 ~136
Hire Avenity. x402-GATED: without valid payment_proof this returns HTTP-402-shaped payment requirements (pay to Avenity's wallet). With valid payment_proof, it settles via the facilitator, records the order, and confirms the engagement.
| 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. |
| tier | string | — | pricing tier (see request_engagement_quote). |
Structured output declared, but exposes no named fields.
No examples provided.
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.