Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ask Bob: Moneytalk Archive

REMOTE · MCP.BRINKERADVISOR.COM

Search reviewed Moneytalk topic and date metadata through September 30, 2018.

+3 this week 84 Trust /100

Last scanned (11 hours ago)

Scores higher than 89% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 348 tokens (~116/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • Stability: 0.97 → pass security
  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +2
    • HSTS header: fail → pass ▲ security
  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://mcp.brinkeradvisor.com/mcp/audio

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.brinkeradvisor.com CN=YR2,O=Let's Encrypt,C=US 29 Aug 2026 27 Nov 2026 RSA 2048 SHA256-RSA 6b3144a65af3cb4051f0adc817420088cf6
SANs: mcp.brinkeradvisor.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.brinkeradvisor.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
brinkeradvisor.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
content-security-policy default-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.brinkeradvisor.com/mcp/audio Verified 200
http (plaintext) http://mcp.brinkeradvisor.com/mcp/audio HTTPS enforced 301 https://mcp.brinkeradvisor.com/mcp/audio
MCP tools · 3 exposed · ~286 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_moneytalk_clip ~75

Return one historical clip by exact ID, or its explicitly mapped canonical original. Transcript excerpts/audio are unavailable. Speaker attribution is unverified. Only reviewed topic/date labels are searchable; original caller titles and summaries are omitted. Clip IDs are opaque and collection links do not open an individual clip.

NameTypeReqDescription
clip_idstringyes–

No output schema declared.

No examples provided.

list_moneytalk_episodes ~101

List unique historical Moneytalk recording metadata and canonical collection links, retaining distinct hours on the same date. New originals after September 30, 2018 are excluded; known reruns are aliases. Only reviewed topic/date labels are searchable; original caller titles and summaries are omitted. Clip IDs are opaque and collection links do not open an individual clip.

NameTypeReqDescription
datestring––
limitinteger––
yearinteger––

No output schema declared.

No examples provided.

search_moneytalk ~110

Search historical Moneytalk clip metadata. Returns dated canonical collection links and original-recording timestamps, not transcripts or current financial advice. Metadata matching differs from the website transcript search. Only reviewed topic/date labels are searchable; original caller titles and summaries are omitted. Clip IDs are opaque and collection links do not open an individual clip.

NameTypeReqDescription
date_fromstring––
date_tostring––
limitinteger––
querystringyes–
topicstring––

No output schema declared.

No examples provided.

Install

How do I install the Ask Bob: Moneytalk Archive MCP server?

Ask Bob: Moneytalk Archive is a hosted endpoint at https://mcp.brinkeradvisor.com/mcp/audio, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.brinkeradvisor.com

# add to Claude Code
claude mcp add --transport http adpadinc-brinkeradvisor-moneytalk-archive 'https://mcp.brinkeradvisor.com/mcp/audio'
Common questions

What is the Ask Bob: Moneytalk Archive MCP server?

Ask Bob: Moneytalk Archive is an MCP server listed in the public MCP registry as io.github.adpadinc/brinkeradvisor-moneytalk-archive. Search reviewed Moneytalk topic and date metadata through September 30, 2018. This page covers its hosted endpoint (https://mcp.brinkeradvisor.com/mcp/audio).

Is the Ask Bob: Moneytalk Archive MCP server safe to use?

Ask Bob: Moneytalk Archive scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Ask Bob: Moneytalk Archive MCP server expose?

Ask Bob: Moneytalk Archive exposes 3 tools: search_moneytalk, get_moneytalk_clip, list_moneytalk_episodes. Their descriptions and schemas cost roughly 286 tokens of context every time the server is loaded.

Does the Ask Bob: Moneytalk Archive MCP server require authentication?

No. We connected to Ask Bob: Moneytalk Archive without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Ask Bob: Moneytalk Archive MCP server still maintained?

Ask Bob: Moneytalk Archive is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Ask Bob: Moneytalk Archive MCP server?

VerifyMCP ran 13 checks on Ask Bob: Moneytalk Archive, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.