Corey James portfolio
REMOTE · COREYJAMES.AI
Fit reports and search over Corey James's work: GPU inference, agent governance, enterprise AI.
Available components
Last scanned (1 hour ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
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 Security49
- 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 13 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- 75% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 579 tokens (~38/item across 15 items; 13 tools + 2 resources), lean.Pass
- 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 Coverage70
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 9% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "contact" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 15 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
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.
- 4 Nov 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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 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.
- 29 Oct 26 +2
- DNSSEC: fail → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 467 → 579 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “fetch” functional
- New tool “search” functional
- 28 Oct 26 52
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 5 Nov 2026 · Probed https://coreyjames.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=coreyjames.ai | CN=WE1,O=Google Trust Services,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 27ea6e9a7e3c1b540e6795385f69e22f |
| SANs: coreyjames.ai, *.coreyjames.ai | ||||||
| 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 secure
Validation of coreyjames.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| coreyjames.ai. | present | 2371 | 13 | Verified |
| coreyjames.ai. | Verified address RRset verified with the apex keys |
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://coreyjames.ai/mcp | Verified | 200 | |
| http (plaintext) | http://coreyjames.ai/mcp | Served over HTTP | 200 |
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 →
contact ~54
Send a message to Corey James through the site's contact form, on behalf of the user. Requires the user's own name and email.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| message | string | yes | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
fetch ~42
Fetch one portfolio document by id (the page path from search): id, title, text (the page as Markdown), url, metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_page ~40
The record for one page by URL: title, result, systems, technologies, stats, lede, quote, evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
list_capabilities ~15
The capabilities the work demonstrates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_ideas ~14
The recurring engineering principles.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_patent_applications ~24
The provisional patent applications (patent pending), with application numbers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_systems ~17
The ten systems with one-line results.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_technologies ~41
Technologies, optionally by kind (language, discipline, platform, framework, protocol, runtime, datastore, hardware, model).
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
No output schema declared.
No examples provided.
match_role ~68
Given a job description or a list of requirements, return an evidence-backed fit report: for each requirement, the pages and figures on coreyjames.ai that demonstrate it, plus the gaps. Cites, never asserts.
| Name | Type | Req | Description |
|---|---|---|---|
| requirements | string | yes | A job description, or requirements one per line. |
No output schema declared.
No examples provided.
scale ~33
The size of the body of work: source lines, commits, languages, systems, stories, ideas, tools, patent applications.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search ~40
Search the portfolio (connector-compatible): returns results with id, title and url. Use fetch with an id for the full document.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
search_portfolio ~56
Search the systems, engineering stories, capabilities, ideas, technologies and patent applications. Returns ranked pages with their measured results and links.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
who ~29
Who this is: name, the name used on patent filings, role, links and how to make contact.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Corey James portfolio MCP server?
Corey James portfolio is a hosted endpoint at https://coreyjames.ai/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 · coreyjames.ai
claude mcp add --transport http ai-coreyjames-portfolio 'https://coreyjames.ai/mcp'
What is the Corey James portfolio MCP server?
Corey James portfolio is an MCP server listed in the public MCP registry as ai.coreyjames/portfolio. Fit reports and search over Corey James's work: GPU inference, agent governance, enterprise AI. This page covers its hosted endpoint (https://coreyjames.ai/mcp).
Is the Corey James portfolio MCP server safe to use?
Corey James portfolio scores 57 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 Corey James portfolio MCP server expose?
Corey James portfolio exposes 13 tools: match_role, search_portfolio, get_page, search, fetch, and 8 more. Their descriptions and schemas cost roughly 473 tokens of context every time the server is loaded.
Does the Corey James portfolio MCP server require authentication?
No. We connected to Corey James portfolio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Corey James portfolio MCP server still maintained?
Corey James portfolio is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.