modelcontextprotocol/example-remote-server

Name: modelcontextprotocol/example-remote-server
Rating: 60 (1 reviews)
Author: modelcontextprotocol

MCPcommunity

modelcontextprotocolMITUpdated 27d agoGitHub

A hosted version of the Everything server - for demonstration and testing purposes, hosted at https://example-server.modelcontextprotocol.io/mcp

This repository provides a complete MCP server implementation that demonstrates all MCP protocol features (tools, resources, prompts, sampling) implements OAuth 2.0 authentication using the recommended separate auth server architectural pattern serves as a learning resource and starting template for building your own MCP servers The Model Context Protocol enables seamless integration between AI…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

76GitHub stars

30Forks

27d agoLast update

Package

Authormodelcontextprotocol

LicenseMIT

Sourcegithub

GitHubmodelcontextprotocol/example-remote-server

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—CVE scan · not run+0/30

→ Not yet scanned — package must be on npm

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

DependenciesNot audited

Tool surface4 tools · none privileged

Security scan✓ CleanvHEAD · 19d ago

CODE…es/mcp/services/mcp.tsVery large base64-looking blob in source

PROMPTdescriptionLinks to undeclared domain: example-server.modelcontextprotocol.io

EvalsNone

IndexedMay 24, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About