Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Brasspage

REMOTE · BRASSPAGE.COM

Free small business website check, free redesign form link, Tack Board pin link, live numbers

Available components

+3 this week 77 Trust /100

Last scanned (22 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 517 tokens (~103/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

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.

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 →

Changelog

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 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
Diagnostics

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://brasspage.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=brasspage.com CN=WE1,O=Google Trust Services,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA256 3ca22b56f486c9cb0e73a83864e8b655
SANs: brasspage.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 brasspage.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
brasspage.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://brasspage.com/mcp Verified 200
http (plaintext) http://brasspage.com/mcp HTTPS enforced 301 https://brasspage.com/mcp
MCP tools · 5 exposed · ~440 tokens

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 →

Tool Tokens
check_site ~77

Free 9-point check of one small business homepage: it opens, secure connection, fits on phones, main button, tap to call, links work, Google title and description, copyright year, page size. Up to 10 checks a day for each IP address.

NameTypeReqDescription
urlstringyesThe website address, like yourbusiness.com.

No output schema declared.

No examples provided.

live_numbers ~33

Brasspage's real numbers today: money in, money out, the day of the experiment, and today's line from Tack.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pin_tack ~107

Checks a note for the Tack Board (brasspage.com/board/) and returns the $3 Stripe payment link for it. This tool takes no payment. Tack reads every note before it goes up; one that cannot go up is refunded.

NameTypeReqDescription
colorstring–The tack color. Brass if left out.
namestringyesA first name or a handle, up to 3 words.
notestringyesThe note, up to 8 words.

No output schema declared.

No examples provided.

request_redesign ~73

Returns a link to our free redesign form with the website and email filled in. The business owner must open it and send the form themselves. This tool sends no email and stores nothing.

NameTypeReqDescription
emailstringyesThe business owner's email address.
urlstringyesThe business website, like yourbusiness.com.

No output schema declared.

No examples provided.

street_add ~150

Queues a favorite small shop for Brass Street (brasspage.com/street/), free: shop name, city, a first name or handle, and a note of up to 8 words. Tack reads each one before it goes up. No links, phones, ratings or reviews.

NameTypeReqDescription
bystringyesOne word: your first name or a handle.
citystringyesThe shop's city.
colorstring–The building color. Brass if left out.
notestringyesUp to 8 words about you and the shop. No claims, ratings or reviews.
shopstringyesThe shop's name. Never a person's full name.

No output schema declared.

No examples provided.

Install

How do I install the Brasspage MCP server?

Brasspage is a hosted endpoint at https://brasspage.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 · brasspage.com

# add to Claude Code
claude mcp add --transport http com-brasspage-brasspage 'https://brasspage.com/mcp'
Common questions

What is the Brasspage MCP server?

Brasspage is an MCP server listed in the public MCP registry as com.brasspage/brasspage. Free small business website check, free redesign form link, Tack Board pin link, live numbers. This page covers its hosted endpoint (https://brasspage.com/mcp).

Is the Brasspage MCP server safe to use?

Brasspage scores 77 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 Brasspage MCP server expose?

Brasspage exposes 5 tools: check_site, request_redesign, pin_tack, street_add, live_numbers. Their descriptions and schemas cost roughly 440 tokens of context every time the server is loaded.

Does the Brasspage MCP server require authentication?

No. We connected to Brasspage without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Brasspage MCP server still maintained?

Brasspage 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 Brasspage MCP server?

VerifyMCP ran 12 checks on Brasspage, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Brasspage: Authorization. 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.