Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

integrations/mcp: expose guard.axios for MCP servers that use axios

未关闭
#57 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
50/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
backend, payments

调研方向

Start with guard.axios as added in #48 and the existing paid_fetch/check_price path in integrations/mcp, which shows how the fetch version is wired. Decide whether the README in integrations/mcp needs only a snippet or a small helper. Done when a test using the real @x402/axios refuses a swapped payee with payee_mismatch and makes zero signatures, and the README snippet runs unchanged.

由索引模型根据 Issue 内容生成。

描述

help wanted integration

guard.axios(instance) landed in the SDK (#48): it records the URL each axios call is made to so Agent Safe judges payments against the right origin, the same way guard.fetch does.

What: make it easy to use from an MCP server built on axios. Either document the pattern in integrations/mcp/README.md with a tested snippet, or add a thin helper if the MCP server's transport needs one. The MCP paid_fetch/check_price path already uses fetch; this is for MCP servers that proxy an axios-based upstream.

Done when: a test with the real @x402/axios shows a swapped payee refused (payee_mismatch) with zero signatures through the axios path, and the README section runs as written.

主要语言
TypeScript
星标
0
派生
0
平均合并
3 小时 51 分钟
30 天内合并 PR
3

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

DeepFirstHQ/deepfirstsearch 的其他 Issue

查看 DeepFirstHQ/deepfirstsearch 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。