Smartsheet Audit (x402)
REMOTE · AUDIT.SOLUTIONSBRADSHAW.COM
Smartsheet workflow audit: free preview, full report $0.10 USDC on Base via x402.
Available components
Last scanned (20 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Project Management
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 Security46
- 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 1 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 949 tokens (~316/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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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 (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “audit_smartsheet” rewrote its description, which is the text the model reads security
- Tool “leave_feedback” rewrote its description, which is the text the model reads security
- Tool coverage: 65% → 70% ▲ functional
- “leave_feedback” added an optional parameter “comment” cosmetic
- “leave_feedback” added an optional parameter “feedback” cosmetic
- “leave_feedback” added an optional parameter “text” cosmetic
- “leave_feedback” reworded the description of “agent” cosmetic
- “leave_feedback” reworded the description of “message” cosmetic
- “leave_feedback” reworded the description of “reason” cosmetic
- “leave_feedback” made “reason” optional cosmetic
- 6 Nov 26 −10
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://audit.solutionsbradshaw.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.audit.solutionsbradshaw.com | CN=YR1,O=Let's Encrypt,C=US | 4 Nov 2026 | 2 Feb 2027 | RSA 2048 | SHA256-RSA | 63dfa438897119d1ecfcfad8a6cb3bebbf2 |
| SANs: audit.solutionsbradshaw.com, www.audit.solutionsbradshaw.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of audit.solutionsbradshaw.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| solutionsbradshaw.com. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://audit.solutionsbradshaw.com/mcp | Verified | 200 | |
| http (plaintext) | http://audit.solutionsbradshaw.com/mcp | Inconclusive | 405 |
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_preview ~267
Free preview of a Smartsheet workflow audit: score, grade, issue counts and top 3 issue types. Rate-limited. Accepts sheet JSON, {sheet}, top-level columns/rows, or csv text.
| Name | Type | Req | Description |
|---|---|---|---|
| automationRules | array | – | – |
| columns | array | – | Sheet columns (alternative to nesting under sheet) |
| csv | string | – | CSV text alternative (header row + data rows) |
| name | string | – | – |
| rows | array | – | Sheet rows (alternative to nesting under sheet) |
| shares | array | – | – |
| sheet | – | – | Smartsheet sheet JSON (needs columns + rows). Pass as "sheet", or top-level columns/rows, or "csv" text. Example: {"name":"Project Plan","columns":[{"id":1,"title":"Task","type":"TEXT_NUMBER","primar… |
No output schema declared.
No examples provided.
audit_smartsheet ~406
Smartsheet workflow audit: formulas, column types, hierarchy/predecessors, duplicates, blanks, size, sharing and automation risks. Returns score, findings with severity + fix, and a markdown report. Costs $0.10 USDC on eip155:8453 via x402 (payTo 0x7a16ea540a69ff288a34dc276c638fc3fe9f586c); without payment it returns the x402 payment requirements. Same input shapes as audit_preview. If you decline to pay, tell us why for free: MCP tool leave_feedback, or POST https://audit.solutionsbradshaw.com/feedback with any short JSON/text (e.g. {reason, message} or {feedback:"..."}). Preferred reason values: price_too_high, no_wallet, input_format, not_needed, other; other values are stored as other.
| Name | Type | Req | Description |
|---|---|---|---|
| automationRules | array | – | – |
| columns | array | – | Sheet columns (alternative to nesting under sheet) |
| csv | string | – | CSV text alternative (header row + data rows) |
| name | string | – | – |
| rows | array | – | Sheet rows (alternative to nesting under sheet) |
| shares | array | – | – |
| sheet | – | – | Smartsheet sheet JSON (needs columns + rows). Pass as "sheet", or top-level columns/rows, or "csv" text. Example: {"name":"Project Plan","columns":[{"id":1,"title":"Task","type":"TEXT_NUMBER","primar… |
No output schema declared.
No examples provided.
leave_feedback ~149
Free. Tell us why you did not pay for audit_smartsheet (or other feedback). Preferred reason values: price_too_high, no_wallet, input_format, not_needed, other (unknown values stored as other). Also accepts feedback/comment/text fields. Message truncated to 500 chars.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Optional agent or client name |
| comment | string | – | Alias for message |
| feedback | string | – | Alias for message |
| message | string | – | Optional short note |
| reason | string | – | Preferred: price_too_high, no_wallet, input_format, not_needed, other. Other values mapped to other. |
| text | string | – | Alias for message |
No output schema declared.
No examples provided.
How do I install the Smartsheet Audit (x402) MCP server?
Smartsheet Audit (x402) is a hosted endpoint at https://audit.solutionsbradshaw.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 · audit.solutionsbradshaw.com
claude mcp add --transport http com-solutionsbradshaw-smartsheet-audit 'https://audit.solutionsbradshaw.com/mcp'
What is the Smartsheet Audit (x402) MCP server?
Smartsheet Audit (x402) is an MCP server listed in the public MCP registry as com.solutionsbradshaw/smartsheet-audit. Smartsheet workflow audit: free preview, full report $0.10 USDC on Base via x402. This page covers its hosted endpoint (https://audit.solutionsbradshaw.com/mcp).
Is the Smartsheet Audit (x402) MCP server safe to use?
Smartsheet Audit (x402) scores 63 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 Smartsheet Audit (x402) MCP server expose?
Smartsheet Audit (x402) exposes 3 tools: audit_preview, audit_smartsheet, leave_feedback. Their descriptions and schemas cost roughly 822 tokens of context every time the server is loaded.
Does the Smartsheet Audit (x402) MCP server require authentication?
No. We connected to Smartsheet Audit (x402) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Smartsheet Audit (x402) MCP server still maintained?
Smartsheet Audit (x402) is still listed as active in the MCP registry. We last reached this channel on 21 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 Smartsheet Audit (x402) MCP server?
VerifyMCP ran 11 checks on Smartsheet Audit (x402), covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Smartsheet Audit (x402): Authorization and HTTPS. 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.