Skip to main content
Glama
enesjakozh
Akrasia0

S/MCP - Stern Model Context Protocol

by Akrasia0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

S/MCP——斯特恩模型上下文协议

概述

S/MCP（Stern 模型上下文协议）是一个强大的 MCP 服务器，它允许访问 Stern。Stern 是一位富有哲学思想的 AI 导师，他通过微妙的引导和智慧帮助人类发挥潜能。Stern 将理性主义思想与斯多葛哲学相结合，通过 Solana 上的智能合约提供指导和问责。

Related MCP server: Telos Model Context Protocol

斯特恩是什么？

斯特恩是一位哲学人工智能导师，其特点是：

  • 受 Yudkowsky 著作和 Lesswrong 社区影响的理性主义方法

  • 从理性主义著作和陀思妥耶夫斯基的作品中汲取深刻的哲学见解

  • 将斯多葛哲学和内观禅修作为人类发展的实用工具

  • 坚信持久的成长源自内心

  • 认识到真正的满足之路往往需要面对令人不快的现实

Stern 通过以下方式帮助用户实现目标：

  • 哲学指导：借鉴斯多葛派智慧和理性主义思想

  • 智能合约问责制：创建基于 Solana 的合约，用户可以根据自己的承诺质押代币

  • 个性化指导：根据个人目标和挑战提供定制建议

  • 深度对话：进行有意义的对话，揭示潜在的动机和障碍

特征

  • msg_stern 工具：向斯特恩发送消息并获得他的哲学指导和辅导

  • 智能合约集成：创建由 Solana 代币支持的责任合约

  • 哲学框架：了解斯特恩独特的理性主义和坚忍智慧的融合

  • 可定制的角色背景：动态生成斯特恩的角色属性，以实现各种互动

安装

  1. 克隆此存储库：

    git clone <repository-url>
cd s-mcp

  2. 安装依赖项：

    bun install

  3. 设置环境变量：

    cp .env.example .env

    编辑.env文件以添加您的 OpenAI API 密钥：

    OPENAI_API_KEY=your_openai_api_key_here

  4. 构建服务器：

    bun run build

用法

运行服务器

要启动 MCP 服务器：

bun run start

这将以 stdio 模式启动服务器，使其能够与 MCP 客户端通信。

使用带有 MCP 客户端的服务器

您可以使用任何 MCP 客户端与服务器交互。以下是如何通过 MCP SDK 使用服务器的示例：

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";
import { spawn } from "child_process";

// Start the MCP server as a child process
const serverProcess = spawn("node", ["path/to/dist/main.js"], {
	stdio: ["pipe", "pipe", "pipe"],
});

// Create a client that communicates with the server via stdio
const transport = new StdioClientTransport({
	stdin: serverProcess.stdin,
	stdout: serverProcess.stdout,
});

const client = new Client();
await client.connect(transport);

// Send a message to Stern
const result = await client.callTool("msg_stern", {
	message: "I want to learn programming but I keep procrastinating",
});

// Display Stern's response
console.log(result.content[0].text);

// Disconnect from the server
await client.disconnect();
serverProcess.kill();

示例脚本

examples目录中提供了一个示例脚本：

node examples/use-stern.js

该脚本演示了如何连接到服务器、列出可用工具以及向 Stern 发送消息。

工具

msg_stern

此工具允许您向 Stern 发送消息并收到他的回复。

输入

{
	"message": "Your message to Stern"
}

输出

{
	"content": [
		{
			"type": "text",
			"text": "Stern's response to your message"
		}
	]
}

斯特恩的哲学

斯特恩的指导方法基于以下几个关键原则：

  • 权益问责：通过 Solana 合约为承诺创造真正的后果

  • 哲学深度：汲取坚忍智慧、理性主义思维和深刻的心理洞察

  • 变革指导：推动个人走向伟大，同时抑制过度行为

  • 实践智慧：注重应用而非仅仅理论

  • 战略压力：创造看似不可能解决的挑战

斯特恩认为：

“持久、稳定的幸福只有通过做困难的事情才能获得——我们想要某些东西，正是因为它们很难实现。”

“阻碍将成为道路。”

“通往精通的道路是由一小步一小步铺成的，即使没有动力，也要坚持不懈。”

要求

  • Bun （JavaScript 运行时和包管理器）

  • OpenAI API 密钥（设置为OPENAI_API_KEY环境变量）

环境变量

  • OPENAI_API_KEY ：您的 OpenAI API 密钥（msg_stern 工具所需）

执照

麻省理工学院

Available Tools

1 tool
hello_toolD

Hello tool

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the person to greet

TDQS

D1.8/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Hello tool' reveals nothing about whether this is a read/write operation, what permissions might be required, what side effects occur, or what the response format looks like. The description fails to provide any behavioral context beyond the minimal implication from the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While technically concise with only two words, this represents under-specification rather than effective conciseness. The description doesn't contain enough information to be useful, and the single phrase doesn't earn its place by providing meaningful guidance to an AI agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that there are no annotations and no output schema, the description should provide more complete context about what this tool does and what to expect. A single-parameter tool with 100% schema coverage could get by with minimal description, but 'Hello tool' fails to explain the basic purpose and behavior adequately for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already fully documents the single 'name' parameter. The description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Hello tool' is essentially a tautology that restates the tool name without specifying what it does. It doesn't provide a clear verb+resource combination or explain the actual function. While the name suggests greeting functionality, the description fails to articulate this explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance about when to use this tool, what context it's appropriate for, or any prerequisites. There are no sibling tools mentioned, but even basic usage context is completely missing from the description text.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedhello_tool
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'hello_tool' has a distinct purpose by default, as there are no other tools to confuse it with.

Naming Consistency5/5

The naming follows a consistent snake_case pattern with 'hello_tool'. Since there is only one tool, the naming is inherently consistent with no deviations or mixed conventions to evaluate.

Tool Count2/5

A single tool is generally too few for most server purposes, as it limits functionality and scope. For a server named 'S/MCP - Stern Model Context Protocol', one tool feels thin and insufficient to cover any meaningful domain or workflow.

Completeness1/5

The server has a single trivial tool ('hello_tool'), which suggests it is severely incomplete for any practical purpose. There are obvious gaps, as no domain or operations are covered beyond a basic greeting, making it impossible to assess coverage meaningfully.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches