Meridary for Agents

io.github.gsMulhernPublished by GitHub account gsMulhernv1.0.0Updated Oct 24, 2026

US retirement modeling for agents: projections, scenario comparisons, and retirement-age analysis.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Lets an assistant run US retirement projections, compare scenarios, and analyze retirement age through a hosted remote endpoint.

What you can do
Meridary for Agents is a remote MCP server for US retirement modeling. According to its description, it supports projections, scenario comparisons, and retirement-age analysis, so an assistant can generate and compare retirement outcomes on request. No individual tools are listed in the supplied material.
When to use it
Useful when someone wants an assistant to model US retirement scenarios, compare alternatives, or examine how different retirement ages affect a plan. It is not a general finance or trading tool.
Requirements
A remote MCP client that supports streamable HTTP, plus OAuth authentication with a Meridary account. No local runtime, packages, environment variables, or headers are declared.
Before you install
OAuth sign-in is required, so the assistant acts on a Meridary account. The material does not describe what personal or financial data is sent to Meridary or how it is stored, and projections are modeling output rather than advice.

Installation

In SourceWeft

  1. Open Meridary for Agents 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/io.github.gsMulhern%2Fmeridary/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": {
    "meridary-for-agents": {
      "type": "http",
      "url": "https://www.meridary.com/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.0.0LatestOct 14, 2026

Score

67% 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
  • 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.