Corey James portfolio

Fit reports and search over Corey James's work: GPU inference, agent governance, enterprise AI.

Should I use this

Quality & Safety

B
Description quality
82%
Schema completeness
54%
Naming quality
93%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (6)

  • LOWTool 'list_systems' description lacks action verbin list_systems
  • LOWTool 'list_capabilities' description lacks action verbin list_capabilities
  • LOWTool 'list_ideas' description lacks action verbin list_ideas
  • LOWTool 'list_patent_applications' description lacks action verbin list_patent_applications
  • LOWTool 'who' description lacks action verbin who
  • LOWTool 'scale' description lacks action verbin scale

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~618Tokens (tool definitions)
~240 BTypical response size
Minimal attention impact (0.48% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "portfolio": {
      "url": "https://coreyjames.ai/mcp"
    }
  }
}

Remote endpoints

https://coreyjames.ai/mcpstreamable-http

What it can do

Tool inventory

Tools (11)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢match_role(requirements)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "requirements": {
      "type": "string",
      "description": "A job description, or requirements one per line."
    }
  },
  "required": [
    "requirements"
  ]
}
🟢search_portfolio(query, kind, limit)

Search the systems, engineering stories, capabilities, ideas, technologies and patent applications. Returns ranked pages with their measured results and links.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string"
    },
    "kind": {
      "type": "string",
      "enum": [
        "system",
        "story",
        "capability",
        "idea",
        "technology",
        "patent-family",
        "tool-group"
      ]
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 25
    }
  },
  "required": [
    "query"
  ]
}
🟢get_page(url)

The record for one page by URL: title, result, systems, technologies, stats, lede, quote, evidence.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string"
    }
  },
  "required": [
    "url"
  ]
}
🟢list_systems

The ten systems with one-line results.

Input Schema

{
  "type": "object",
  "properties": {}
}
🟢list_capabilities

The capabilities the work demonstrates.

Input Schema

{
  "type": "object",
  "properties": {}
}
🟢list_ideas

The recurring engineering principles.

Input Schema

{
  "type": "object",
  "properties": {}
}
🟢list_technologies(kind)

Technologies, optionally by kind (language, discipline, platform, framework, protocol, runtime, datastore, hardware, model).

Input Schema

{
  "type": "object",
  "properties": {
    "kind": {
      "type": "string"
    }
  }
}
🟢list_patent_applications

The provisional patent applications (patent pending), with application numbers.

Input Schema

{
  "type": "object",
  "properties": {}
}
⚪who

Who this is: name, the name used on patent filings, role, links and how to make contact.

Input Schema

{
  "type": "object",
  "properties": {}
}
⚪scale

The size of the body of work: source lines, commits, languages, systems, stories, ideas, tools, patent applications.

Input Schema

{
  "type": "object",
  "properties": {}
}
🟡contact(name, email, message)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string"
    },
    "email": {
      "type": "string"
    },
    "message": {
      "type": "string"
    }
  },
  "required": [
    "name",
    "email",
    "message"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded11 tools