com.thechrisgrey/mcp

MCPcommunitylive
v1.0.0com.thechrisgreyUnknownUpdated 5mo agoGitHub

Search Christian Perez's blog, read posts, and ask about his work, podcast, and writing.

Personal website for Christian Perez (@thechrisgrey) | Founder & CEO of Altivum Inc. | Former Green Beret (18D Special Forces Medical Sergeant) | Bronze Star Recipient | Host of The Vector Podcast | Author of "Beyond the Assessment" Environment Variables -------|------------| Frontend | React 19, TypeScript 5, Vite 5 (Vitest 4, ESLint 10 flat config) | Styling | Tailwind CSS 4 (CSS-first config,…

Endpoint healthlive
checked 9 days ago · 432ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1Forks
5mo agoLast update
Package
Authorcom.thechrisgrey
LicenseUnknown
Version1.0.0
Sourcemcp-registry
GitHubthechrisgrey/thechrisgrey
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

Source not readable3mo ago

The repository archive could not be read at scan time (tarball exceeds size cap), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

Personal website for Christian Perez (@thechrisgrey) | Founder & CEO of Altivum Inc. | Former Green Beret (18D Special Forces Medical Sergeant) | Bronze Star Recipient | Host of The Vector Podcast | Author of "Beyond the Assessment" Environment Variables -------|------------| Frontend | React 19, TypeScript 5, Vite 5 (Vitest 4, ESLint 10 flat config) | Styling | Tailwind CSS 4 (CSS-first config, Oxide engine) | Routing | React Router 7 | CMS | Sanity.io (blog content) | AI Chat | Amazon Bedrock…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.