1. Conduid
  2. Search
  3. App History Actors
MCP server · Search

App History Actors

Discover the faces behind the protocol. This example MCP application renders interactive cards for the key actors of the MCP apps specification, showcasing how to serve structured metadata through an MCP-APP compliant interface.

Unclaimed last commit 8 months ago search
34Low

Scored a month ago · breakdown

About App History Actors

App History Actors is an MCP server published by GiladShoham in the Search category: discover the faces behind the protocol. This example MCP application renders interactive cards for the key actors of the MCP apps specification, showcasing how to serve structured metadata through an MCP-APP compliant interface.

Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/GiladShoham/mcp-app-history-actors

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Tools (1)

get-history-actorsReturns information about MCP specification contributors

Parameters not published.

Ask AI

✦

Ask AI about App History Actors

Powered by Claude · Grounded in docs

I know everything about App History Actors. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

6 checks have not been run yet.

Questions

About App History Actors

How do I install App History Actors?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is App History Actors safe to use with an AI agent?

Its trust score is 34 out of 100 (low). Conduid hasn't run static security checks on this repository yet, so review the source yourself before granting it credentials. It has no ConduID identity yet, so agent calls to it are not receipted.

Is App History Actors still maintained?

The last commit was 8 months ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.