MCP.Market

Pforge MCP server

by paiml·io.github.paiml/pforge·v0.1.2·3 stars

Zero-boilerplate MCP server framework with declarative YAML configuration

B73/100grade B
What users say
No reviews yet
Be the first
Safety scan
B73/100

full report

Adoption
New

3 stars

Reviews

Write one

Nobody has reviewed Pforge yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Pforge tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualityno auth information5/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 73/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Pforge compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
73/100
higher than 39% of 48,255 servers
GitHub stars
3
more than 80% of 28,688 servers

Install Pforge in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Pforge repository's README, as published. We do not edit it. Read it on GitHub

pforge

A declarative framework for building Model Context Protocol (MCP) servers using YAML configuration.

MCP Server

Registry Name: io.github.paiml/pforge

pforge is available in the Model Context Protocol (MCP) Registry. Install it via:

# Via Cargo (recommended)
cargo install pforge-cli

# Then run as MCP server
pforge serve

For Maintainers: See MCP Registry Publishing Guide for publishing instructions.

What is pforge?

pforge lets you define MCP servers in YAML instead of writing boilerplate code. It's built on top of pmcp (rust-mcp-sdk) and generates optimized Rust code from your configuration.

Quick example:

forge:
  name: my-server
  version: 0.1.0
  transport: stdio

tools:
  - type: native
    name: greet
    description: "Greet someone"
    handler:
      path: handlers::greet_handler
    params:
      name: { type: string, required: true }

Installation

# From crates.io
cargo install pforge-cli

# From source
git clone https://github.com/paiml/pforge
cd pforge
cargo install --path crates/pforge-cli

Quick Start

# Create new project
pforge new my-server
cd my-server

# Run the server
pforge serve

The scaffolded project includes a working example handler. Edit pforge.yaml to add more tools, then implement handlers in src/handlers/.

Handler Types

pforge supports four handler types:

  1. Native - Rust functions with full type safety
  2. CLI - Execute shell commands
  3. HTTP - Proxy HTTP endpoints
  4. Pipeline - Chain multiple tools together

See the book for detailed examples of each type.

Language Bridges

pforge provides language bridges for building MCP servers in your preferred language:

Deno/TypeScript Bridge

Build type-safe MCP servers using TypeScript and Deno with native performance:

import { PforgeBridge } from "https://raw.githubusercontent.com/paiml/pforge/main/bridges/deno/bridge.ts";

const bridge = new PforgeBridge();

bridge.register({
  name: "greet",
  description: "Greet a user by name",
  handler: (input: { name: string }) => ({
    success: true,
    data: { message: `Hello, ${input.name}!` },
  }),
});

const result = await bridge.execute("greet", { name: "Alice" });
console.log(result.data);

Features:

  • Type-safe handler definitions with TypeScript generics
  • Runtime schema validation with no external dependencies
  • O(1) handler lookup performance
  • Both sync and async handler support
  • 74+ tests passing with full quality gates

Documentation: bridges/deno/README.md

Coming Soon

  • Python bridge (FFI-based with asyncio support)
  • Go bridge (CGo-based with goroutine support)
  • Node.js bridge (Native addon with N-API)

Documentation

  • Book - Complete guide with examples and comparisons
  • Architecture - Technical design details
  • User Guide - Usage guide
  • Implementation Status - Current project status
  • CLAUDE.md - Development workflow for contributors

Examples

  • hello-world - Minimal native handler example
  • calculator - Math operations with tests
  • rest-api-proxy - HTTP handler examples

Project Status

Version: 0.1.2

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Pforge: common questions

Is Pforge MCP server safe?
Mostly: it is graded B (73/100). Read the Pforge safety report
Does Pforge need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Pforge maintained?
The last commit was 34 days ago (2026-10-01). The latest release is v0.1.2.
How does Pforge compare with other MCP servers?
safety score 73/100 (higher than 39% of 48,255 servers); github stars 3 (more than 80% of 28,688 servers). Full comparison.

More from paiml →