Jeremy Twogood — Portfolio

com.jeremytwogoodPublished by jeremytwogood.comOfficial publisherv1.0.0Updated Oct 24, 2026

MCP server for Jeremy Twogood, Toronto video producer & editor. Projects, reel, resume, booking.

VerifiedStreamable HTTPWeb executable

Overview

AI-generated overview

A remote MCP server for Jeremy Twogood's portfolio, covering video projects, reel, resume, and booking.

What you can do
This server exposes Jeremy Twogood's portfolio content to an assistant over a remote HTTP endpoint. According to its description, it covers projects, a reel, a resume, and booking. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Useful when someone wants an assistant to look up or reference this Toronto video producer and editor's portfolio material, such as projects, reel, resume, or booking details, without browsing the site manually.
Requirements
A remote MCP client that supports streamable HTTP, connecting to the provider's endpoint. No authentication, environment variables, or headers are declared, and no local package or runtime is needed.
Before you install
No credentials, payments, or write actions are declared. Because it is a remote endpoint, requests go to the provider's server; the manifest lists no tools, so verify what data is exposed before relying on it.

Installation

In SourceWeft

  1. Open Jeremy Twogood — Portfolio in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.jeremytwogood%2Fportfolio/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "jeremy-twogood-portfolio": {
      "type": "http",
      "url": "https://jeremytwogood.com/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.