Raze
REMOTE · RAZEGROWTH.COM · SCANNED SEP 20
Explore Raze services, pricing, projects, availability, and confirmed introduction bookings.
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 Security63
- 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 10 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 581 tokens (~58/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management89
- Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 81% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Raze MCP server?
Raze is a hosted endpoint at https://razegrowth.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 · razegrowth.com
claude mcp add --transport http edinabazi-raze 'https://razegrowth.com/mcp'
{
"mcpServers": {
"edinabazi-raze": {
"url": "https://razegrowth.com/mcp"
}
}
} {
"servers": {
"edinabazi-raze": {
"type": "http",
"url": "https://razegrowth.com/mcp"
}
}
} [mcp_servers.edinabazi-raze] url = "https://razegrowth.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"edinabazi-raze": {
"type": "remote",
"url": "https://razegrowth.com/mcp",
"enabled": true
}
}
} openclaw mcp add edinabazi-raze --url 'https://razegrowth.com/mcp' --transport streamable-http
mcp_servers:
edinabazi-raze:
url: "https://razegrowth.com/mcp" {
"McpServers": {
"edinabazi-raze": {
"Transport": "http",
"Url": "https://razegrowth.com/mcp"
}
}
} assistant mcp add edinabazi-raze -t streamable-http -u 'https://razegrowth.com/mcp'
{
"mcpServers": {
"edinabazi-raze": {
"type": "http",
"url": "https://razegrowth.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.
- 12 Sept 26 −2
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “get_pricing” was removed ▼ security
- New tool “get_engagements” functional
- 26 Aug 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
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 5 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_pricing” rewrote its description, which is the text the model reads security
- 31 Jul 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
- 30 Jul 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
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://razegrowth.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=razegrowth.com | CN=YR2,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | RSA 2048 | SHA256-RSA | 6c4f4514f3e4942c9198a26342f2856f5c7 |
| SANs: razegrowth.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 razegrowth.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| razegrowth.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), autoplay=(), camera=(), display-capture=(), geolocation=(), gyroscope=(), microphone=(), payment=(), tools=(self), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://razegrowth.com/mcp | Verified | 200 | |
| http (plaintext) | http://razegrowth.com/mcp | HTTPS enforced | 308 | https://razegrowth.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 →
create_booking ~194
Create a real Cal.com booking for Raze. Only call this after the visitor selected an available slot and explicitly confirmed the booking.
| Name | Type | Req | Description |
|---|---|---|---|
| attendeeEmail | string | yes | – |
| attendeeName | string | yes | – |
| confirmed | boolean | yes | Must be true after explicit visitor confirmation. Calls without true are rejected. |
| guests | array | – | Optional guest email addresses. Maximum 5. |
| needs | array | yes | The visitor's most urgent needs. |
| notes | string | – | Context the visitor wants Raze to review before the call. |
| services | array | yes | Raze services the visitor wants to discuss. |
| start | string | yes | Selected slot start time as a future UTC ISO date-time ending in Z. |
| timeZone | string | yes | Attendee IANA time zone, for example America/New_York. |
| website | string | yes | Visitor website or company URL. Bare domains such as company.com are acceptable. |
No output schema declared.
No examples provided.
get_available_slots ~135
Check available Cal.com time slots for the Raze introduction event. This is read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| duration | integer | – | Optional event duration in minutes. |
| end | string | yes | End of the search range as an ISO 8601 date or date-time. Must be after start and within 31 days. |
| format | string | – | Cal.com slot response format. Defaults to range. |
| start | string | yes | Start of the search range as an ISO 8601 date or date-time. |
| timeZone | string | – | IANA time zone for returned slots, for example America/New_York. Defaults to UTC. |
No output schema declared.
No examples provided.
get_booking_profile ~29
Get the Cal.com booking profile, event slug, booking URL, and required fields for agent bookings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_booking_url ~20
Get the public human-facing booking URLs for Raze.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_engagements ~24
Get Raze engagement options, services, timelines, and CTA URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_project ~26
Get one public project case study summary by slug.
| Name | Type | Req | Description |
|---|---|---|---|
| projectslug | string | yes | – |
No output schema declared.
No examples provided.
get_site_summary ~20
Get the public Raze site summary and key URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_projects ~16
List public Raze project case studies.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_resources ~15
List public Raze resource collections.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_services ~15
List public Raze service pages.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Raze MCP server?
Raze is an MCP server listed in the public MCP registry as io.github.edinabazi/raze. Explore Raze services, pricing, projects, availability, and confirmed introduction bookings. This page covers its hosted endpoint (https://razegrowth.com/mcp).
Is the Raze MCP server safe to use?
Raze scores 76 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 Raze MCP server expose?
Raze exposes 10 tools: get_site_summary, get_engagements, list_services, list_projects, get_project, and 5 more. Their descriptions and schemas cost roughly 494 tokens of context every time the server is loaded.
Does the Raze MCP server require authentication?
No. We connected to Raze without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Raze MCP server still maintained?
Raze 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.