Atlas / MCP servers / junfanz1 / Interoperable Agent System

Interoperable Agent SystemCAUTION

Name: Interoperable Agent System
Author: junfanz1

mcp/junfanz1/interoperable-agent-system

MCP server by junfanz1 · agentic framework · ai · langchain · Audited 2026-10-08

This project demonstrates a decoupled real-time agent architecture that connects LangGraph agents to remote tools served by custom MCP (Modular Command Protocol) servers. The architecture enables a flexible and scalable multi-agent system where each tool can be hosted independently (via SSE or STDIO

Verdict

CAUTION

Grade

Trust score

88 /100

Exposed tools

2 1r · 1w · 0d

Transport

sse · stdio

License

—

Stars

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

[](https://mseep.ai/app/junfanz1-mcp-multiserver-interoperable-agent2agent-langgraph-ai-system)

Decoupled Architecture: Engineered a modular system where LangGraph-based agents orchestrate LLM workflows while delegating tool execution to remote MCP servers via both SSE and STDIO transports.
Advanced Asynchronous Programming: Utilized Python’s async/await for non-blocking I/O, ensuring concurrent execution of multiple tools and scalable real-time communication.
MCP & LangGraph Integration: Demonstrated deep expertise in integrating Modular Command Protocol (MCP) with LangGraph and LangChain, enabling seamless transformation and invocation of distributed tools.
Flexible Multi-Server Connectivity: Designed a MultiServerMCPClient that supports 1:1 bindings to various tool servers, highlighting the system’s ability to integrate diverse environments (local, cloud, containerized).
Robust Agent-to-Tool Communication: Implemented detailed client sessions, handshake protocols, and dynamic tool discovery, ensuring reliable execution and interaction between agents and MCP servers.
Forward-Looking Interoperability: Laid the groundwork for an Agent2Agent protocol, aiming for an ecosystem where AI agents can share capabilities, coordinate actions, and securely exchange context and data.

🚀 Project Purpose

This project aims to:

Decouple **LLM

Read from source at commit b132ee46795fOBSERVED · 2026-10-08

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.

claude-code

claude mcp add shellserver --env OPENAI_API_KEY=${OPENAI_API_KEY} -- uvx shellserver

claude-desktop

{
  "mcpServers": {
    "shellserver": {
      "command": "uvx",
      "args": [
        "shellserver"
      ],
      "env": {
        "OPENAI_API_KEY": "${OPENAI_API_KEY}"
      }
    }
  }
}

Exposed tools (2)

1 read · 1 write · 0 destructive.

Tool	Risk	Description
`get_weather`	read	Get weather for location.
`run_terminal_command`	write

Trust audit

CAUTIONgrade B · trust 88/100 Install with care. The audit found things worth knowing before you trust its output.

Layer	What it checks	Result
L0	Provenance & inventory	WARN
L1	Static analysis of the code	PASS
L2	Instruction surface (what it tells the agent)	PASS
L3	Class-specific surface	PASS
L4	Behavioural (sandbox)	SKIPPED

What the source does

Filesystem: none-observed
Network: none-observed
Shell: declared (2 observation(s))
Dependencies: pinned
Secrets in source: none-found

Findings (4)

MEDIUMInventory / provenance · inv.binary · CWE-1104

.DS_Store

.DS_Store

Why it matters. a compiled or binary member cannot be reviewed from source

Fix. ship source, or explain the binary in the README

MEDIUMInventory / provenance · inv.binary · CWE-1104

shellserver/__pycache__/server.cpython-313.pyc

server.cpython-313.pyc

Why it matters. a compiled or binary member cannot be reviewed from source

Fix. ship source, or explain the binary in the README

LOWInventory / provenance · inv.hidden_file · CWE-1104

.DS_Store

.DS_Store

Why it matters. hidden member outside the usual dotfiles

Fix. review its purpose

LOWInventory / provenance · inv.no_license · CWE-1104

Why it matters. no LICENSE file and no repo licence

Fix. add a licence

Gates applied: no_behavioural_pass, no_license.

Audited 2026-10-08 · audit v0.4.1 · source sha b132ee46795ffull audit observations/trust-audit/mcp-server/junfanz1__interoperable-agent-system.json · Report an issue / request a re-scan

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

Date	Source	Verdict	Grade	Score	Change
2026-10-08	`b132ee46795f`	CAUTION	B	88	first audit

Questions

What is the Interoperable Agent System MCP server?

What tools does Interoperable Agent System expose?

2 in total: 1 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Interoperable Agent System safe to connect to an agent?

With care. The audit graded it B (88/100) and found 4 things worth knowing before you trust this server, listed below with the exact line each was found on.

What credentials does Interoperable Agent System need?

It reads OPENAI_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.

How does Interoperable Agent System run?

It speaks sse and stdio, so it runs as a local process your client starts. It is published on PyPI as shellserver.

How current is this page?

The grade is for one exact copy of the source (b132ee46795f), read on 2026-10-08. The repository is watched and re-audited when it changes.

Source	junfanz1/mcp-multiserver-interoperable-agent2agent-langgraph-ai-system
PyPI	`shellserver`
Transports	sse · stdio
Credentials it reads	`OPENAI_API_KEY`
Activity	pushed 443d ago