LivingMeta — AI in Research

ai.livingmetaPublished by livingmeta.aiOfficial publisherv1.1.0Updated Oct 24, 2026

Read-only MCP over the LivingMeta AI-in-Research corpus: 12,400 papers, gaps, priority agenda.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Read-only MCP access to the LivingMeta AI-in-Research corpus of 12,400 papers, research gaps and a priority agenda.

What you can do
  • Search and read the LivingMeta AI-in-Research corpus of about 12,400 papers.
  • Look up identified research gaps and the priority agenda drawn from that corpus.
  • All access is read-only, so the assistant can consult the material but not change it.
When to use it
Useful when you want an assistant to ground answers about AI research literature, open gaps or research priorities in this specific curated corpus rather than the open web.
Requirements
A remote streamable HTTP endpoint at ai-in-research.livingmeta.ai; OAuth authentication is required. No environment variables or headers are declared.
Before you install
Access requires signing in through OAuth, so the provider sees your account identity and query activity. The corpus is a single third-party curated collection, so coverage and freshness are limited to what it contains.

Installation

In SourceWeft

  1. Open LivingMeta — AI in Research in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.livingmeta%2Fai-in-research/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "livingmeta-ai-in-research": {
      "type": "http",
      "url": "https://ai-in-research.livingmeta.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.